FYI - https://issues.apache.org/jira/browse/INFRA-26154
Best, tison. tison <[email protected]> 于2024年9月25日周三 10:15写道： > > > How about redirecting them to "dev@" > > Given the traffic to Curator, I agree with this suggestion. > > > in BookKeeper (and in Pulsar), long time ago, we had a script that copied > > all the JIRA issues to GH, we could use that > > Yeah .. Let me create an INFRA ticket today to move this forward. > > Best, > tison. > > Enrico Olivelli <[email protected]> 于2024年9月11日周三 21:07写道： > > > > +1 to use Github > > > > in BookKeeper (and in Pulsar), long time ago, we had a script that copied > > all the JIRA issues to GH, we could use that > > > > > > Enrico > > > > Il giorno mar 20 ago 2024 alle ore 17:28 Kezhu Wang <[email protected]> ha > > scritto: > > > > > Hi tison, > > > > > > > we have commits@ to handle this activities > > > > > > I think it might be a good to leave "commits@" to commit diffs only. > > > The "commits@" mailing lists of ZooKeeper[1] and Beam[2] are pretty > > > clean. How about redirecting them to "dev@" or a separate "github@"(or > > > other naming) ? I saw > > > https://lists.apache.org/[email protected]. > > > > > > The rest are all good to me. I believe we can tweak all these in > > > migration. > > > > > > [1]: https://lists.apache.org/[email protected] > > > [2]: https://lists.apache.org/[email protected] > > > > > > Best, > > > Kezhu Wang > > > > > > On Tue, Aug 20, 2024 at 8:50 AM tison <[email protected]> wrote: > > > > > > > > > Do you have any plan for evaluation and agreement ? > > > > > > > > If we have a lazy consensus here, I can open a JIRA ticket for moving > > > > this forward. > > > > > > > > > 1. How do we migrate existing jiras ? > > > > > > > > IIRC the INFRA team has an SOP for this. > > > > > > > > > 2. How to write the release note ? A CHANGELOG.md ? > > > > > > > > Yes. That's possible. But GitHub's CHANGELOG is mainly based on PR > > > > while our JIRA release notes are based on tickets. As long as the PRs > > > > map to issues, it can be a viable workaround. > > > > > > > > > 3. Should we redirect github issues to the mailing list ? > > > > > > > > This is a MUST while IIRC we have commits@ to handle this activities. > > > > See [1][2]. > > > > > > > > [1] > > > https://github.com/apache/curator/blob/eeee4c63be6e2377ab9fa8a70f9406dc410ee7d2/.asf.yaml#L40-L43 > > > > [2] > > > https://github.com/apache/opendal/blob/d001321b0f9834bc1e2e7d463bcfdc3683e968c9/.asf.yaml#L42-L46 > > > > > > > > Best, > > > > tison. > > > > > > > > Kezhu Wang <[email protected]> 于2024年8月10日周六 00:20写道： > > > > > > > > > > Hi tison, > > > > > > > > > > +1 from my side. > > > > > > > > > > I am positive about github issues over jira. > > > > > 1. No more account registration approvals. It increases the bar for > > > > > newcomers. Also, it is hard for us to be capable of spam detectors > > > > > while not hurting the passions of newcomers. > > > > > 2. One account and permission systems. JIRA requires contributor > > > > > permission to get assigned by default. > > > > > 3. Github is much much more prevalent in the open source world. > > > > > > > > > > I do believe that JIRA is powerful, but I think it imposes a pretty > > > > > high contribution bar for Apache Curator. > > > > > > > > > > Do you have any plan for evaluation and agreement ? > > > > > > > > > > 1. How do we migrate existing jiras ? > > > > > 2. How to write the release note ? A CHANGELOG.md ? > > > > > 3. Should we redirect github issues to the mailing list ? > > > > > > > > > > > > > > > Best, > > > > > Kezhu Wang > > > > > > > > > > On Fri, Aug 9, 2024 at 4:53 PM tison <[email protected]> wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > I noticed that we don't commit anything in the past two months. > > > > > > However, the JIRA issue tracker should still have quite a few open > > > > > > issues. > > > > > > > > > > > > Perhaps moving those issues to GitHub issues can make it easy to > > > track > > > > > > and handle. We don't heavily use JIRA anyway. The release note can > > > > > > be > > > > > > generated with GitHub also. > > > > > > > > > > > > This is my personal preference, but I can see potential developers > > > may > > > > > > prefer an integrated solution on GitHub also. > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > Best, > > > > > > tison. > > >
