THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Question | Answer | ||||||||
|---|---|---|---|---|---|---|---|---|---|
1. What will be the process to give permissions to contributors on GitHub after they have filed their ICLA? | (Jacques Le Roux ): Anybody should be allowed to create issues (see point 3 below). (Michael Brohl ): yes, but not anyone can provide patches afaik. They must file an ICLA first and then get specific permissions. (Jacques Le Roux ): No, ICLA are only for committers . This is not to be confused with our policy where ICLAs are required to get write access to our wiki. It was a time where there was a check box in Jira. It has been removed, because when someone submit a patch (either on Jira or by any other way) s/he implicitely renounce to her right on the code giving the right to the ASF. Then comes SPAM and how to handle it. Here are 2 answers: | ||||||||
| 2. How do we control the permissions for committers and contributors on GitHub? | (Jacques Le Roux ): Same than point 1. It's open, like in GH you can also have SPAM in Jira once you have created an account... (Michael Brohl ) we have fine grained permissions set in Jira, the answer does not refer to that. (Jacques Le Roux ): what does it add? What do we need to control? | ||||||||
3. What do we offer for contributors who are not able or willing to maintain their own repositories and follow the PR process? | This was already answered with the point 3. We should We can ask Infra to offer the "Issues" feature (a top button) in our GH mirrors. You can then report in GH as you would to in Jira. It mostly offers the same possibilities than Jira. I guess it's not a problem for Infra to open the feature, but that needs to be confirmed | ||||||||
4. When we publish a new release we update Jira versions to reflect the change. This information is useful to group Jira tickets by version. Is there a similar feature in GitHub? | (Jacques Le Roux ) Is the point 4 not answering this question? Also see See related Jacopo's answer in my comment below (Michael Brohl ) this is not answered as long as the process is clear. How is it used in practice? (Jacques Le Roux ) Beside Jacopo's answer, why do we want that? What is the purpose? | ||||||||
5. Has GitHub tools alike elaborated search in Jira, e.g. with filters? Can existing filters/views be migrated from Jira to GitHub? Examples for filters:
| (Jacques Le Roux ) Incidently, I made a seach in Jira yesterday. I was looking for "Canonical url". I could not find a result, but Markmail allowed me to find it: Jira:
Markmail: https://ofbiz.markmail.org/search/?q=%22Canonical+url%22 So, though I very like Jira search because it can be right to the point, but it's not always accurate. I can then trust Markmail, which is easier to use than Pony when you are lazy. Because it searches on all MLs for all time and you can then filter by many ways. It's also still very fast.(Michael Brohl ) I am able to find 4 results for "canonical url" and even more with using "canonical". You should use the search correctly. (Jacques Le Roux ) Can you please share your research or a filter? Mine was <<project = OFBIZ AND status in (Open, "In Progress", Reopened) AND text ~ "\"Canonical url\"">> (Michael Brohl ) you have set a filter to the status which markmail does not. I will now stop this because if you do not take your time to thoroughly lay out you arguments and confusing everything with even more confusing answers, this is useless. Sorry Jacques.Part of your markmail results are from the users list which has nothing to do with Jira.(Jacques Le Roux ) yes MarkMail searches are wide. Most of the time you need to filter after. This answer is also simplifying the answer to one specific search term which does not qualify the search. And without similar tests of the GitHub search this finding is useless. You should remove this answer.(Jacques Le Roux ) It was only to illustrate my point. As I said I "very like Jira search" and know a bit about it  I'll enhance the question to be more clear what I mean with search functions/filters : I think that this should not stop us in our choice. I have created a comment to move a conversation with Michael in. Else please simply look at Searching on GitHub documentation. | ||||||||
| 6. What about dashboards, like https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12310603 ? We need to keep in mind that such one-page information (provided by the project) is key when decision makers (the potential adopters) review the product. | (Jacques Le Roux ): Do we really need that as a requirement? I know we are a peculiar TLP at the ASF. But I would be interested to have some fedback from other TLPs wich have resigned using Jira and are only using GH. Not speaking about all the succesful not ASF projects which are using GH and are more successul than us :/ I'm not even sure that decision makers are aware of such dashboards and fancy Jira stuff or use them in their decisions... |
References
- https://rocketmq.apache.org/docs/pull-request/
- https://issues.apache.org/jira/plugins/servlet/project-config/OFBIZ/administer-versions?status=released-unreleased
- https://help.github.com/en/github/managing-your-work-on-github/creating-an-issue
- "gren" is a small helpful robot that will do for you just create a release from a tag and compile the release notes using issues or commits.