Here are the specific questions that I am looking to answer regarding
the different systems. Please feel free to share your thoughts on this
thread.
Also, as mentioned earlier, if you want to head up an investigation of
any of those products and provide us with a report, that would be much
appreciated. This process will help us make a decision based on
community feedback.
-Stephano
-------------
Please describe how [Phabricator/Gitlab/Gerrit/Github] fulfills the
following feature requirements. These questions are a guide, so feel
free to add any information you feel is pertinent. Also, screenshots or
other examples are highly desirable. Think about how our system works
today and use that as a reference for what you are describing (e.g.
today we do it this way, but with [new-system] it will work like this).
Please send responses directly to me at [email protected],
so that any attachments can be shared (our mailing list does not
currently support attachments).
1. No Lock-In - What automated data export is available?
We want to be able to leave and take all our data with us. "Data" here
includes: review comments, pull requests / patches (including metadata),
old (rejected) pull requests and metadata, issue tracker entries and
comments (if issue tracker included). This archiving should be
automated, not something we do by hand.
2. Easy Administration - Are there any scripts or custom code required
after initial setup? We would like to do as little customizing as possible.
3. Flexible Workflow - Can we use email patches / email review as well
as pull requests / web UI review?**
3a. Can we can attach review comments to specific code *and* commit
message locations?
3b. Are the comments faithfully translated to notification emails
(including the locations in code the comment is addressing)?
3c. Are old topic branches (rejected or updated pull requests)
available even after being rejected? (i.e. are they ever deleted?)
3d. Is plain text supported in code review comments?
**To be clear, it is acceptable if the system handles only pull requests
and a web UI. We do require, however, a *read-only* email notification
system that thoroughly documents our process.
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
