Oh! Actually...GitHub Wiki's are actually git repos! I'll be sure to mention that to Infra if they say "no" (with hopes of making it a..."well...not yet..." instead). ^_^
-- http://bigbluehat.com/ http://linkedin.com/in/benjaminyoung ________________________________ From: Benjamin Young Sent: Wednesday, May 17, 2017 5:37:30 PM To: [email protected] Subject: Re: [VOTE] Move issues & wiki to GitHub So. You may be spot on about the Wiki, but I'm confident it's possible for Issues. For instance: https://github.com/apache/couchdb/issues <https://github.com/apache/couchdb/issues>https://github.com/apache/couchdb-fauxton/issues Also, I'm currently at ApacheCon (are you here?!) and it came up in this talk: https://apachecon2017.sched.com/event/9zvX/navigating-the-incubator-trenches-john-d-ament-sparta-systems Folks in the room (including John) seemed to imply that it's quite possible to do both--with Infra's help (as they're the actual "admin" account holders on GitHub). I'll ask the folks here about it again, but there's evidence (re: CouchDB) that's it's at least possible for Issues...and maybe Wiki. :) I'll report back! Benjamin -- http://bigbluehat.com/ http://linkedin.com/in/benjaminyoung ________________________________ From: Richard Eckart de Castilho <[email protected]> Sent: Wednesday, May 17, 2017 5:22:07 PM To: [email protected] Subject: Re: [VOTE] Move issues & wiki to GitHub Hi Benjamin, I am possibly not up-to-date with the ASF policy, but I had the impression that it is usually preferred to keep issues on the Apache Infrastructure, i.e. Jira. I assume that the GIT repo is mirrored onto the Apache Infrastructure, but that this is not (yet?) possible with issues / wiki. So in order to keep all project-related information on the Apache Infrastructure, I suppose that it would be useful to stick to Confluence / Jira and use GitHub only for merge requests and friends. As I said: I may be wrong. Just wanted to raise the flag in case I'm not wrong ;) -- Richard > On 17.05.2017, at 23:16, Benjamin Young <[email protected]> wrote: > > Currently, our issues are on Jira > > https://issues.apache.org/jira/browse/ANNO/<https://issues.apache.org/jira/browse/ANNO> > > <https://issues.apache.org/jira/browse/ANNO>and our wiki is on Confluence: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67633804 > > > Now that we're on GitHub (thanks to the ASF Infra team! [1]) for pull > requests and forks, I'd like to also propose that we start using GitHub for > our Issues and Wiki. > > > This should increase activity here by lowering the bar to contribution--as > folks will no longer need to sign up for a Confluence and Jira account + ask > for the permission to be changed *before* editing the wiki or commenting on > an issue. > > > Also, for those of us coming from the Annotator.js or W3C communities, we're > already setup with GitHub accounts, so this should streamline the bulk of our > experiences. > > > Per ASF policy & process, this is "[VOTE]" thread. So...the other committers > (Randall, Dinesh, etc) have 72 hours to +1/0/-1 this decision. If everyone's > +1, I'll file the ticket with infra (or they can!) to get things moving. If > not, then we'll keep discussing and decided what we'd do instead and why, etc. > > > Cool? :) > > > If you're on the Initial Committers list may (afaik) vote as well--even if > they're not yet setup with accounts at the ASF, etc--because voting happens > on this mailing list: > > https://cwiki.apache.org/confluence/display/ANNO/Annotator+Proposal#AnnotatorProposal-InitialCommiters > > > k. Send in your votes! > > > Thanks, > > Benjamin > > > [1] https://issues.apache.org/jira/browse/INFRA-14127 > > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung
