Open dcloud opened 10 years ago
@dcloud @kaitlin How about we use issues for discussion and we use the repo for sharing more re-usable knowledge.
Issues: Problems, or bugs, people are having with specific use cases and tools. A place to put issues that do not fit with elsewhere easily.
Repo: Create a folder for each challenge and for different categories of knowledge. People can add and make pull requests to update the Repo.
:thumbsup: on using this repo for issues. I was thinking pdfliberation/pdf-hackathon for IDing hackathon teams (and contact info) might work and we'd use this repo for the more long term stuff. So the pdf-hackathon would be first stage for people this weekend and other repos would be for permanent members of the organization. But either way, we could migrate/prune information as needed.
I opened an issue #2 for people to comment on if they want to be added to the organization. I may write a script that auto-adds those people to the @pdfliberation/members general purpose team.
Using this repo for longer term issues makes sense to me.
Greg Elin P: 917-304-3488 E: gregelin@gitmachines.com
Sent from my iPhone
On Jan 17, 2014, at 12:16 PM, Daniel Cloud notifications@github.com wrote:
on using this repo for issues. I was thinking pdfliberation/pdf-hackathon for IDing hackathon teams (and contact info) might work and we'd use this repo for the more long term stuff. So the pdf-hackathon would be first stage for people this weekend and other repos would be for permanent members of the organization. But either way, we could migrate/prune information as needed.
I opened an issue #2 for people to comment on if they want to be added to the organization. I may write a script that auto-adds those people to the @pdfliberation/members general purpose team.
— Reply to this email directly or view it on GitHub.
There should be a note in Readme explaining the two repos. (Currently on mobile and cannot changes. I can add later.)
Greg Elin P: 917-304-3488 E: gregelin@gitmachines.com
Sent from my iPhone
On Jan 17, 2014, at 12:16 PM, Daniel Cloud notifications@github.com wrote:
on using this repo for issues. I was thinking pdfliberation/pdf-hackathon for IDing hackathon teams (and contact info) might work and we'd use this repo for the more long term stuff. So the pdf-hackathon would be first stage for people this weekend and other repos would be for permanent members of the organization. But either way, we could migrate/prune information as needed.
I opened an issue #2 for people to comment on if they want to be added to the organization. I may write a script that auto-adds those people to the @pdfliberation/members general purpose team.
— Reply to this email directly or view it on GitHub.
I'm looking for suggestions about how to organize people around code projects, documenting knowledge, evaluating existing tools, etc.
After talking with @gregelin and then @kaitlin, it occurred to me that Github Issues could serve as a forum that lives in the same place as the projects we create. So this seems like a good place to start the discussion of how we can organize people during and post-hackathon.