Greetings. If any one needs meeting summary, below is. I was not till the
end and so, it is not complete. Wished to mention.
Thanks @saifi for driving this.
@all Pardon me if anything is missing/change needed. Please add as reply
*Tools looked in*
- Issue tracker
- Documentation
*Issue tracker*
- Issue tracker should be able to preserve the history of commits
happened beyond to the main (strikr) branch
- For this, there are two approaches. *One* in which pull request to
mainline provides info about changes. *Another* in which, all history
is pulled and be part of the mainline
- Issue tracker should have capability to do multi-site collaboration
- If Strikr project takes patch of Linux kernel, then tracker should
be able to link external project patch. Gitlab allows to link. For this
ref ID is used
- We observed that code hosting platform must include Issue tracker
natively, not as an external entity
- Looked following examples
- codeberg *https://codeberg.org <https://codeberg.org>, *
- Gitlab
- Linux kernel issue tracker,
- google chrome issue trackers
- Different open-source teams are using different tools since they are
different in organization structure.
*Collaboration*
- Strikr team is expected to collaborate with Linux Kernel, doxygen by
submitting patches,
*Pull request validation via mail*
- Pull request validation should be automated.
- In long term, strikr should try to achieve the Linux kernel mail based
validation. Linux kernel team uses automated approach (via script) to
validate the proposed patch and accepts/rejects it.
*Documentation*
- doxygen tool generates class relationship diagram which will be
useful. Need to follow coding practice for such documentation.
Warm Regards,
Deepak
