Title: Concept: The Drupal Project
Section: Understanding Drupal
File name: understanding-project.txt
Covers: Drupal as an open-source project and community, how work gets done, issues, contributed projects for modules, themes, distributions.
Attribution
See https://userguide_new-drupal.dev.devdrupal.org/guidelines/guidelines.htm...
<<understanding-project>>::
Written by https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon].
Checklist for this phase
- Does it follow the template?
- Have the comments and placeholder text been removed from the template?
- Is everything the topic was supposed to cover included, and nothing extra?
- If there are @todo notes, are they clear?
- If there are images included, do they include instructions for how to redo them in a comment? (Note: Screenshots do not need to be perfect. Just make a rough cut.)
- Is attribution provided?
Comment | File | Size | Author |
---|---|---|---|
#12 | understanding-project.txt | 2.07 KB | jhodgdon |
Comments
Comment #1
michaellenahan CreditAttribution: michaellenahan at erdfisch commentedI think the biggest problem here is to decide the scope - how far to go into the sub-topics.
For content, the following pages may be of use:
The introductory slides here --> https://docs.google.com/presentation/d/1GXK1dBSe6_QMhSkNwsgocWynlzdQFrMU...
https://www.drupal.org/about
https://www.drupal.org/drupal-faq
https://www.drupal.org/getting-started/before/overview
Comment #2
jhodgdonYes, that is a good point.
Hm... Let's see. Maybe something like:
- A few sentences about the project/community as a whole: it's open-source, world-wide, diverse, comes together for a common purpose of improving Drupal [Note that we have a separate topic planned about the GPL license, and other topics about the software, so here just talk about the community and project.]
- A few sentences about "teams" within the community as a whole: Projects (Drupal core, modules, themes, distributions), other work the community does (documentation on drupal.org, security team -- see https://www.drupal.org/security, Working Groups for governance -- see https://www.drupal.org/governance/)
- A few sentences about how we communicate with each other to get work done: issues (for bugs and discussions of improvements for each "team"), IRC (for instant discussions of issues, also for support), team meetings (via Google Hangouts or Skype or something similar), groups.drupal.org (forums), Stack Exchange (support), local meetups, regional conferences, DrupalCon
- A sentence or two about the Drupal Association and its role (maintaining and paying for *.drupal.org, funding community projects through grant programs, DrupalCon)
Does that make sense? We probably want this to end up something like 3-6 paragraphs. I'm not sure about the right order of those ideas either, but I think the order there would probably make sense?
Comment #3
jhodgdonAdding checklist to summary
Comment #4
jhodgdonI'll take this one on.
Comment #5
jhodgdonI followed the outline I had made in comment #3, with the exception of the idea of talking about IRC and other ways to connect to the community -- we have a separate topic for that (thougths-connecting) so I put that in Related Topics instead.
Anyway, here's a first pass... thoughts?
Comment #6
michaellenahan CreditAttribution: michaellenahan at erdfisch commentedI think it's good! Setting to RTBC.
A small comment - I'm not even sure about this myself - would be to have the various examples in this sentence into bullet points:
Comment #7
jhodgdonThanks! We can take care of things like that during the copy editing phase. Not a bad idea; probably not worth holding this up for either.
Comment #8
michaellenahan CreditAttribution: michaellenahan at erdfisch commentedHi! I'm looking at the spreadsheet https://docs.google.com/spreadsheets/d/1ov0FyJhKrJe7PYvohzV5UrrLyRaVCy2A... and wondering what's needed to get this moved to the EDIT stage.
Is it that someone else (other than me or jhodgdon) still needs to review understanding-project.txt?
Comment #9
jhodgdonAll that needs to be done is a final review by Joe and a commit to add it to the Git source repository. I don't normally commit the topics I wrote. ;)
Comment #10
jhodgdonSummary update.
@eojthebrave - this one still needs final review and commit sometime... thanks!
Comment #11
eojthebraveIn comment #2 you said, "- A few sentences about how we communicate with each other to get work done: issues (for bugs and discussions of improvements for each "team"), IRC (for instant discussions of issues, also for support), team meetings (via Google Hangouts or Skype or something similar), groups.drupal.org (forums), Stack Exchange (support), local meetups, regional conferences, DrupalCon"
But this isn't really addressed in the text you've got here. Is this something you think we should cover? I feel like at a minimum we could add something about how Drupal.org is the central communications hub for the community. Thoughts?
Other than that, I like this, and think it looks good. Once the above is addressed (either added, or an argument made for not adding it) I'm happy to commit this.
Comment #12
jhodgdonAh, yeah, forgot that. So we actually have another topic for connecting with the community, which I've recently written a draft for on #2541592: Write thoughts-connecting.txt. We also have a Support topic, which hasn't been written yet.
Hm, I see that thoughts-connecting is already linked. Let's just add thoughts-support, and I'll also put the link in the text so it's clearer how it's connected. How's this?
I'm also adding a list item about the issues queues to the thoughts-connecting topic on that other issue, because I somehow managed to leave that out.
Comment #14
eojthebraveThat works for me. I just want to make sure that at some point we make it clear the Drupal.org is currently the communities hub. And I'm fine with that being in another topic.
Thanks Jennifer, and @michaellenahan. I'll get this committed now.