You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@annotator.apache.org by Benjamin Young <by...@bigbluehat.com> on 2017/05/17 21:16:21 UTC

[VOTE] Move issues & wiki to GitHub

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

Re: [VOTE] Move issues & wiki to GitHub

Posted by Benjamin Young <by...@bigbluehat.com>.
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: dev@annotator.incubator.apache.org
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 <re...@apache.org>
Sent: Wednesday, May 17, 2017 5:22:07 PM
To: dev@annotator.incubator.apache.org
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 <by...@bigbluehat.com> 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


Re: [VOTE] Move issues & wiki to GitHub

Posted by Robert Knight <ro...@hypothes.is>.
I’m not on the initial committer list but as someone who has contributed to the anchoring libraries that are likely to end up in this project and who has often needed to link to related upstream bug reports from GitHub issues in Hypothesis projects, I’m in favour of this.

Kind Regards,
Rob.

> On 18 May 2017, at 10:19, Edward Silverton <e....@gmail.com> wrote:
> 
> +1
> 
> On Thu, 18 May 2017 at 01:43 Randall Leeds <ra...@gmail.com> wrote:
> 
>> If infra gives the okay on this, I'm for it.
>> I'll be watching the CouchDB progress on this.
>> 
>> On Wed, May 17, 2017, 16:10 Nick Kew <ni...@apache.org> wrote:
>> 
>>> On Wed, 17 May 2017 21:37:30 +0000
>>> Benjamin Young <by...@bigbluehat.com> wrote:
>>> 
>>> -1 on your VOTE.  This needs discussion first, as Richard
>>> has already highlighted.
>>> 
>>>> So. You may be spot on about the Wiki, but I'm confident it's
>>>> possible for Issues. For instance:
>>> 
>>> Some (many?) Apache projects accept issues submitted either on
>>> Github or Apache.  That's certainly OK, and makes life easy for
>>> outsiders coming to the project through either route.  Github
>>> pull requests are also popular in Apache projects.  But I'm
>>> not sure about github-only: did John's talk suggest that?
>>> 
>>> --
>>> Nick Kew
>>> 
>> 


Re: [VOTE] Move issues & wiki to GitHub

Posted by Edward Silverton <e....@gmail.com>.
+1

On Thu, 18 May 2017 at 01:43 Randall Leeds <ra...@gmail.com> wrote:

> If infra gives the okay on this, I'm for it.
> I'll be watching the CouchDB progress on this.
>
> On Wed, May 17, 2017, 16:10 Nick Kew <ni...@apache.org> wrote:
>
> > On Wed, 17 May 2017 21:37:30 +0000
> > Benjamin Young <by...@bigbluehat.com> wrote:
> >
> > -1 on your VOTE.  This needs discussion first, as Richard
> > has already highlighted.
> >
> > > So. You may be spot on about the Wiki, but I'm confident it's
> > > possible for Issues. For instance:
> >
> > Some (many?) Apache projects accept issues submitted either on
> > Github or Apache.  That's certainly OK, and makes life easy for
> > outsiders coming to the project through either route.  Github
> > pull requests are also popular in Apache projects.  But I'm
> > not sure about github-only: did John's talk suggest that?
> >
> > --
> > Nick Kew
> >
>

Re: [VOTE] Move issues & wiki to GitHub

Posted by Randall Leeds <ra...@gmail.com>.
If infra gives the okay on this, I'm for it.
I'll be watching the CouchDB progress on this.

On Wed, May 17, 2017, 16:10 Nick Kew <ni...@apache.org> wrote:

> On Wed, 17 May 2017 21:37:30 +0000
> Benjamin Young <by...@bigbluehat.com> wrote:
>
> -1 on your VOTE.  This needs discussion first, as Richard
> has already highlighted.
>
> > So. You may be spot on about the Wiki, but I'm confident it's
> > possible for Issues. For instance:
>
> Some (many?) Apache projects accept issues submitted either on
> Github or Apache.  That's certainly OK, and makes life easy for
> outsiders coming to the project through either route.  Github
> pull requests are also popular in Apache projects.  But I'm
> not sure about github-only: did John's talk suggest that?
>
> --
> Nick Kew
>

Re: [VOTE] Move issues & wiki to GitHub

Posted by Nick Kew <ni...@apache.org>.
On Wed, 17 May 2017 21:37:30 +0000
Benjamin Young <by...@bigbluehat.com> wrote:

-1 on your VOTE.  This needs discussion first, as Richard
has already highlighted.

> So. You may be spot on about the Wiki, but I'm confident it's
> possible for Issues. For instance:

Some (many?) Apache projects accept issues submitted either on
Github or Apache.  That's certainly OK, and makes life easy for
outsiders coming to the project through either route.  Github
pull requests are also popular in Apache projects.  But I'm
not sure about github-only: did John's talk suggest that?

-- 
Nick Kew

Re: [VOTE] Move issues & wiki to GitHub

Posted by Benjamin Young <by...@bigbluehat.com>.
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 <re...@apache.org>
Sent: Wednesday, May 17, 2017 5:22:07 PM
To: dev@annotator.incubator.apache.org
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 <by...@bigbluehat.com> 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


Re: [VOTE] Move issues & wiki to GitHub

Posted by Richard Eckart de Castilho <re...@apache.org>.
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 <by...@bigbluehat.com> 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


Re: [VOTE] Move issues & wiki to GitHub

Posted by TB Dinesh <di...@servelots.com>.
+1 for this move

Re: [VOTE] Move issues & wiki to GitHub

Posted by Robert Sanderson <az...@gmail.com>.
+1 to moving to Github issues and wiki

On Wed, May 17, 2017 at 2:16 PM, Benjamin Young <by...@bigbluehat.com>
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
>



-- 
Rob Sanderson
Semantic Architect
The Getty Trust
Los Angeles, CA 90049

Re: [VOTE] Move issues & wiki to GitHub

Posted by Randall Leeds <ra...@apache.org>.
Thanks, Benjamin!

On Mon, May 22, 2017, 07:58 Benjamin Young <by...@bigbluehat.com> wrote:

> Given all the +1's and that Nick's -1 was connected to the feasibility
> only, I've gone ahead and submitted a ticket with Infra:
>
> https://issues.apache.org/jira/browse/INFRA-14200
>
> And...within moments...Infra had enabled them for us!!
> https://github.com/apache/incubator-annotator
> https://github.com/apache/incubator-annotator-website
> <https://github.com/apache/incubator-annotato><
> https://github.com/apache/incubator-annotato>
>
>
> We now have Issues, Wiki, and Projects turned on for both those repos.
>
> I'll be leaving pointers from the old paces to the new places and updating
> the website.
>
> Thanks, all!
> Benjamin
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>
> ________________________________
> From: Sasha Goodman <em...@sashagoodman.com>
> Sent: Thursday, May 18, 2017 2:48:33 PM
> To: dev@annotator.incubator.apache.org
> Subject: Re: [VOTE] Move issues & wiki to GitHub
>
> +1
>
> On Thu, May 18, 2017 at 10:34 AM Randall Leeds <ra...@apache.org> wrote:
>
> > For reference, here's the thread from CouchDB about similar:
> >
> > http://mail-archives.apache.org/mod_mbox/couchdb-dev/201705.mbox/browser
> >
> > On Thu, May 18, 2017 at 5:16 AM Robert Casties <
> > casties@mpiwg-berlin.mpg.de>
> > wrote:
> >
> > > +1 I'm fine with having everything on github if Apache is ok with this.
> > >
> > > Robert C.
> > >
> > >
> >
>

Re: [VOTE] Move issues & wiki to GitHub

Posted by Benjamin Young <by...@bigbluehat.com>.
Given all the +1's and that Nick's -1 was connected to the feasibility only, I've gone ahead and submitted a ticket with Infra:

https://issues.apache.org/jira/browse/INFRA-14200

And...within moments...Infra had enabled them for us!!
https://github.com/apache/incubator-annotator
https://github.com/apache/incubator-annotator-website
<https://github.com/apache/incubator-annotato><https://github.com/apache/incubator-annotato>


We now have Issues, Wiki, and Projects turned on for both those repos.

I'll be leaving pointers from the old paces to the new places and updating the website.

Thanks, all!
Benjamin

--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
From: Sasha Goodman <em...@sashagoodman.com>
Sent: Thursday, May 18, 2017 2:48:33 PM
To: dev@annotator.incubator.apache.org
Subject: Re: [VOTE] Move issues & wiki to GitHub

+1

On Thu, May 18, 2017 at 10:34 AM Randall Leeds <ra...@apache.org> wrote:

> For reference, here's the thread from CouchDB about similar:
>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201705.mbox/browser
>
> On Thu, May 18, 2017 at 5:16 AM Robert Casties <
> casties@mpiwg-berlin.mpg.de>
> wrote:
>
> > +1 I'm fine with having everything on github if Apache is ok with this.
> >
> > Robert C.
> >
> >
>

Re: [VOTE] Move issues & wiki to GitHub

Posted by Sasha Goodman <em...@sashagoodman.com>.
+1

On Thu, May 18, 2017 at 10:34 AM Randall Leeds <ra...@apache.org> wrote:

> For reference, here's the thread from CouchDB about similar:
>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201705.mbox/browser
>
> On Thu, May 18, 2017 at 5:16 AM Robert Casties <
> casties@mpiwg-berlin.mpg.de>
> wrote:
>
> > +1 I'm fine with having everything on github if Apache is ok with this.
> >
> > Robert C.
> >
> >
>

Re: [VOTE] Move issues & wiki to GitHub

Posted by Randall Leeds <ra...@apache.org>.
For reference, here's the thread from CouchDB about similar:

http://mail-archives.apache.org/mod_mbox/couchdb-dev/201705.mbox/browser

On Thu, May 18, 2017 at 5:16 AM Robert Casties <ca...@mpiwg-berlin.mpg.de>
wrote:

> +1 I'm fine with having everything on github if Apache is ok with this.
>
> Robert C.
>
>

Re: [VOTE] Move issues & wiki to GitHub

Posted by Robert Casties <ca...@mpiwg-berlin.mpg.de>.
+1 I'm fine with having everything on github if Apache is ok with this.

Robert C.