Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate programs #16

Open
sarathms opened this issue Dec 22, 2013 · 3 comments
Open

Duplicate programs #16

sarathms opened this issue Dec 22, 2013 · 3 comments

Comments

@sarathms
Copy link
Contributor

I detected at least one duplicate set of programs (refer #14 and #10). I think @prometheansacrifice and @pcputta and everyone else who will contribute should coordinate.

One way is to open an issue here on which program/set/lab/sem you are going to take up so that others will know before picking the next one. Close the issue once you are done. You may mention 'closes #issue_number_here' in the commit message to automatically close the related issue.

@viggyprabhu @shijiltv @sant0sh Share if you think there's a better way to coordinate.

@ghost ghost assigned viggyprabhu Dec 22, 2013
@ManasJayanth
Copy link
Contributor

@sarathms Well I did realize that this morning when I saw the list of PRs here. 👍 for the idea.

@importerror
Copy link
Member

@sarathms Sounds good!
Another way which i can think of is by maintaining the syllabus.md file.
Its better to update all the programs in the syllabus.md file. When a program is being added then we can add a link in syllabus.md which will direct to that program being added.
So the ones which are not added will be known and can worked upon.

@ManasJayanth
Copy link
Contributor

@sarathms I discovered this today. We can now make a list of programs completed and pending in an Issue. This can help us make things more systematic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants