Problem/Motivation
Github recently added new community tools which lints projects for their own open-source community recommendations, one of which is that "a CONTRIBUTING
file tells your audience how to participate in your project.".
Proposed resolution
Add a core/CONTRIBUTING.txt
to Drupal's repository, with the contents of Drupal's Ways to get involved documentation.
I suggest putting it in whichever folder holds MAINTAINERS.txt
(i.e.: another piece of documentation you'd probably want to read if you wanted to interact with the Drupal community). In Drupal 8, MAINTAINERS.txt
is in the core
sub-directory; in Drupal 7 MAINTAINERS.txt
is in the root folder.
I suggest we make it a .txt
(as opposed to a markdown document / .md
) to be consistent with other documentation in that directory.
I suggest we use the text from https://www.drupal.org/contribute because:
- that's a pretty comprehensive jumping-off point regardless of the reader's specialty (i.e.: it's for more than just developers),
- the text on that page doesn't change as often as the pages it links to (i.e.: less work to keep the file in-sync with the page on d.o), and,
- we have a lot of documentation on contributing, arguably more than we can reasonably expect someone to read in a single file.
Remaining tasks
Write a patch- Review and feedback
- RTBC and feedback
- Commit
- Discuss how to backport to 7.x
User interface changes
None.
API changes
None.
Data model changes
None.
Comment | File | Size | Author |
---|---|---|---|
#37 | comparison.png | 126.1 KB | brahmjeet789 |
#34 | Add-Contributing-txt-2886296-34.patch | 4.66 KB | kanav_7 |
#33 | Contributing-txt-2886296-33.patch | 4.67 KB | mohit1604 |
#31 | Add-Contributing-txt-2886296-31.patch | 4.69 KB | kanav_7 |
#20 | contributingtxt-2886296-20.patch | 4.67 KB | dani3lr0se |
|
Comments
Comment #2
mparker17Here's a patch for the
8.4.x
branch. Reviews welcome!Comment #3
mparker17(tagging as a novice issue)
Comment #4
mparker17(formatting changes to the issue summary)
Comment #5
naveenvalechaDo we have the documentation page for Drupal 8?
Comment #6
mparker17@naveenvalecha, the link was copied directly from https://www.drupal.org/contribute : I'm tempted to say that's a discussion for the maintainers of that documentation page. For reference, the D8 theming guide is at https://www.drupal.org/docs/8/theming
Comment #7
dawehnerjust some drive by review
I think we should point to IRC/Slack instead
This points to all issues instead of the core specific ones
Comment #8
mgiffordI like this idea. Neat suggestion by Github. Thanks for getting this started Matt!
I'd suggest:
- Adding a section for accessibility.
- Adding something about social media. "Thank those users or the projects that make your work a success"
- Could also ask folks to blog about it and add links back to the projects they use
@naveenvalecha good point. Maybe best to point to https://www.drupal.org/docs/8 for now. Though really not sure that the D8 docs have a
Theming HowTo that is updated.
@dawehner 1. agreed. Who uses Mailing lists? 2. I'd agree that it should focus on the core specific issues. I do think though that core does have a responsibility to point people to broader Drupal issues.
Comment #10
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedHi all. I created a new patch that addresses the feedback in #5, #7 and #8. I made a new patch, rather an interdiff because I made it for 8.5.x. I hope this was ok. I'd be happy to do it another way if necessary. Thanks for your time and help. :)
Comment #12
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedHmmm. Something is weird. It's showing that I deleted the file instead of adding it. I'll fix it. My apologies. :(
Comment #13
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedHere is the patch showing that I actually added the file. Sorry all. :(
Comment #14
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedThird time is the charm, right? I'm very sorry. :(
Comment #15
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedComment #17
volkswagenchickI tested the patch using Simplytest.me and the patch applied smooth. Since it is documentation, there was no UI testing.
I reviewed the patch for grammar and spelling, tested all links, and reviewed formatting.
One minor nitpick:
Line breaks should be at 80 characters as per Drupal documentation standards
Comment #18
volkswagenchickMarking as needs work.
Comment #19
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedI will work on this later today and update. Thanks for reviewing. :)
Comment #20
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedHere is a new patch that addresses the line wrapping at 80 characters. I made an interdiff, but it didn't recognize the difference in line wrapping. So here is the new patch with line wrapping at 80 characters. It was already set to 80 characters, but the difference was that my editor was set to automatically wrap at 80 characters rather than just manually wrapping at 80. Setting to manual wrapping at 80 is what fixed this.
Comment #21
volkswagenchickI used simplytest.me to test the patch and it applies. The nitpick is comment #17 was addressed.
Grammar, formatting, and readability are good.
The issues in comments #5 and #7 were addressed were appropriate links.
An accessibility section was added to address comment #8.
Since this is documentation there are no UI issues to test. Marking as RTBC.
Thanks for all the work on the issue.
Comment #22
larowlanTagging for reviews
Comment #23
larowlanMy 2c: I would prefer we just link to the docs on drupal.org for the following reasons:
- these things have a tendency to get out of date
- requiring a patch to update it is arduous
- anyone can update docs pages
But let's see what others think first
Comment #24
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commented@larowlan, that makes sense. I actually like that idea better. :)
Comment #25
xjmFWIW I agree with #23. What's in this patch is great! But let's put this work into the handbook and then just have the file link the handbook page so that it can stay current.
Comment #26
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedSounds good. Thanks for the feedback @xjm. What is the process for putting this into the handbook? Or is that something that I could do? Thanks so much for your feedback and help. :)
Comment #27
larowlanLet's wait for a final review from a product manager, @xjm has given it the release manager once-over.
In terms of getting it in the handbook, if you can edit the page, all good.
If not, it would need an issue filed in the documentation queue
Comment #29
Ivan Berezhnov CreditAttribution: Ivan Berezhnov as a volunteer and at Drupal Ukraine Community for Levi9 commentedComment #31
kanav_7 CreditAttribution: kanav_7 at Google Summer of Code commentedUpdated in drupal 8.6.x
Comment #32
volkswagenchickLooks good, One minor fix needed, leaving status as need works.
Should have a blank line at the end of the file
Comment #33
mohit1604 CreditAttribution: mohit1604 at Google Summer of Code commentedThis should be fine.
Comment #34
kanav_7 CreditAttribution: kanav_7 at Google Summer of Code commented@volkswagenchick : Fixed that. Please Check Now.
Comment #35
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedAssigning as Needs Review per #34.
Comment #36
cilefen CreditAttribution: cilefen at Institute for Advanced Study commentedI love this issue. That said this would be more maintainable as a brief message followed by one hyperlink to the contribution guide. We have as much documentation in git to deal with as we can already.
Comment #37
brahmjeet789 CreditAttribution: brahmjeet789 as a volunteer and at gai Technologies Pvt Ltd commented@mohit1604 and @kanav_7 i have viewed your patch but i am unable to see any diifernece in both patches i am attaching screenshot of diif please check
Comment #44
jibranDo we need a section on security here?
Comment #48
smustgrave CreditAttribution: smustgrave at Mobomo commentedBrought this up on the #needs-review-queue-initiative with @quietone