Additional Guidelines for README?

[kadamwhite]

Other questions for discussion:

• Is this limited to members of the BostonWP community?
• Do you have to have authored the plugin you submit?
• Who or what is going to manage pull requests?

We should also probably link up the WordPress development guidelines right from the readme; it would also be helpful to have examples of the settings API, and counterexamples of what not to do (could we use the repo wiki for this?)

I'm sure there are other questions to talk through, but I just wanted to kick off the conversation—As background, [https://github.com/blog/1124-how-we-use-pull-requests-to-build-github](this is the way Github uses pull requests to manage internal projects), which I have found very helpful in structuring group projects. It keeps all the management out in the open.

[kadamwhite]

One other thought: Something truly awesome about Automattic's _s theme is that it includes tokens throughout the code files to allow easy find-and-replace. If we are going to look at potentially providing ways for people to build or export subsets of these plugins, should we look at encouraging people to use a _bwp_ prefix for function names, in the same manner in which underscores uses _s_...?

See https://github.com/Automattic/_s/blob/master/readme.txt#L21 for an example of what I am talking about

[jonbish]

@kadamwhite I like the bwp idea. Haven't used _s yet. Definitely more on my radar now.

[kadamwhite]

If you approve, I can update the readme to encourage tokenized bwp function names.

As for the other questions, I think the first two bullets in this thread are the ones I'm most curious about your thoughts on. For example, could we reach out to the _s team to see if they mind us abstracting some of that theme's functions.php code into small plugins, or are we looking for this to be a "Made in MA" kind of thing? Personally I prefer that we open this up and encourage its use as a general resource, I think regionality is kind of silly on github, but given the name of the org I wanted to see what people thought.

[jonbish]

I think we should definitely open it up to people outside of MA. Also, do we need to reach out to _s? I think we can just grab what we like and reference them as the authors. Same for any functionality we like from the default WordPress themes.

[kadamwhite]

I probably will as common courtesy, but as long as we don't step on licensing terms it's no different than forking the repo