Check out [1] for a list of projects that are moving to GitHub issues. As long as the PMC approves, INFRA will support the switch.
(Side note: kinda ironic that you have to file a JIRA to move to GitHub issues :-) +1 for experimenting with the geode-kafka-connector repo. Once we see how that goes, I’m in favor of having a larger conversation about migrating entirely from JIRA to Github. I’ve been thinking about doing this for awhile so thanks for taking the first step Naba! I think it will be a better experience for all and really help all contributors not have to deal with multiple systems to get stuff done. [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20INFRA%20AND%20text%20~%20%22GitHub%20issues%22 <https://issues.apache.org/jira/issues/?jql=project%20=%20INFRA%20AND%20text%20~%20%22GitHub%20issues%22> > On Mar 22, 2020, at 8:44 AM, Jacob Barrett <jbarr...@pivotal.io> wrote: > > +1 couldn’t be anymore onboard with this. Maybe I missed a discussion about > this earlier but are we certain that ASF rules allow for this? I would think > as long as all the notifications go through the the mailing lists and gitbox > is setup they would be ok. Just given that neither of your examples are ASF > projects I am a little concerned we are putting the cart before the horse > here. > > -Jake > > >> On Mar 21, 2020, at 5:17 PM, Nabarun Nag <n...@apache.org> wrote: >> >> Hello team, >> >> We are planning to experiment with using Github issues and wiki for the >> Apache project *Geode-Kafka-Connector. *(not Apache Geode project). Please >> do give your vote on this as we need to send the vote link to infra to >> activate it. >> >> *Why are we doing this ? / Advantages* : >> 1. *Unified location* to have documentation, code and issue tracking. >> 2. Leverage Github tools like Github pages to create websites hosting >> information about the project. >> 3. No separate JIRA accounts or permission required to create issues. >> 4. This will have *no impact on the broader Geode community* as right now >> only 3-4 developers involved in this project. >> 5. *This is an experiment.* If things do not work out we can always revert >> back to the traditional way of having separate JIRA, documentation, >> websites etc. >> >> *Precedence*: >> 1. Kubernetes uses the github issues >> 2. RabbitMQ uses github issues. >> >> >> *NOTE: *- Please be cordial and do not use any condescending language and >> absolutely no bullying. >> - Please treat this email as a professional business email and maintain >> email etiquette while replying. >> >> Regards >> Nabarun
