On Fri, May 08, 2015 at 02:00PM, Roman Shaposhnik wrote: > On Fri, May 8, 2015 at 1:49 PM, William Markito <[email protected]> wrote: > >> 1. Our website. Currently http://geode.incubator.apache.org > >> doesn't have any content. Two questions that we need to > >> answer are: > >> 1.1. What tool will we use to create html > >> 1.2. How the source code for the website is going to be > >> managed. > >> Personally, I'd be pushing really hard to manage a website > >> as part of the repository so I can just run: gradle site and > >> not worry about much else > >> > > > > +1 for that and I'd suggest to have a branch (which we already have named > > asf-site) for hosting the website source. Then as part of the release > > process it would be required to update the website as well. A Jira > > component named "website" would hold all the tickets related to that. > > That branch is actually their for just publishing. It is expected to contain > exactly 100% the same html that would show up once you hit > http://geode.incubator.apache.org > > What I would like to propose is that we use markdown (what we're currently > using) integrated with Gradle the same way that Hadoop does it (although > it does it with Maven). E.g.: > > https://github.com/apache/hadoop/tree/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site
If using Gradle - why not to go with asciidoctor, which can be rendered to MD or HTML5, yet is a pretty great system for docs and web-content? Check what groovy and gradle guys are doing with it! > > Anybody against having geode-site at the same level as all the > other folders? > > >> 2. A typical ASF way for signaling that you would like to > >> contribute something is to open up a JIRA and follow up > >> with the patch. What about our Github integration? I'd suggest > >> the following: anytime a PR comes, a committers who is > >> interested in helping to get the patch in opens up a corresponding > >> JIRA. That way we can have a central source of truth > >> on ASF JIRA while still enabling the workflow. > >> > > > > +1 here but we just need to make sure the GitHub integration happens and > > that when we commit/accept the PR's they're closed at GH. > > Yes. Sorry I should've mentioned that GH doesn't allow for merging > pull request into R/O mirrors of ASF projects. The way to close a PR > is to commit the change with a special commit message: > https://help.github.com/articles/closing-issues-via-commit-messages/ > > > Also what about comments ? Is there any integration about that so when > > comments happens in one side they make to the other ? (Jira - GH / GH - > > Jira) > > That's the tricky one. See my reply to Justin. Personally I prefer > as much commenting to be done on ASF JIRA as possible. However, > given that GH PR comments are being forwarded to our dev@geode > ML and thus archived I'd be fine with those comments NOT being > on JIRA. > > >> 4. Finally, the question of committing the change. I'll chime > >> in on a separate thread that you guys have already created, > >> but for now (given that there's a final code drop coming soon) > >> I'd like to propose that Dan, William and Anthony should > >> be required to give any patch an explicit +1 before it gets > >> committed. This is ABSOLUTELY NOT a suggestion for > >> having gatekeepers. This is just a suggestion of what we > >> do between now and when the final code drop comes. Meantime > >> we'll have a separate discussion on how roadmap for the > >> project gets maintained and how anything that doesn't require > >> studying code base for a few month could be committed to > >> the project. > > This is actually where I'd really like folks to comment. I have a few > things I need to commit already ;-) > > Thanks, > Roman.
