On Mon, 26 Jul 2021, Deepak Kumar wrote:
- Strikr team is expected to collaborate with Linux Kernel, doxygen by
submitting patches,
"expected to collaborate" ?
No, that is both incorrect and misleading !
What i said was,
"when we build our software we use components that are released by
up-stream projects.
in the case of Linux kernel we may download a patch that showed up as a
potential
solution in the kernel issue tracker."
in the other instance, what i said was,
"when we were building custom libstdc++ documentation we encountered,
which we discussed
with GCC folks who suggested that we discuss with doxygen folks, which
is a up-stream
project for Strikr.
Then we discussed the issue using the Github issue tracker with doxygen
folks
https://github.com/doxygen/doxygen/issues/8295
and with the fix made available as a patch we could build our local doxygen
binary."
Both the illustrations were used to highlight that when working with free
software, there are multiple upstream projects that we interact with via issue
trackers that they use.
Now, many of the patches may not make it to the updated packages on a GNU/Linux
distro (eg. doxygen in pacman and doxygen that we buildfrom git are different.)
Hence we need a mechanism in Strikr issue tracker to keep track of all the
up-stream patches that we used when working on a specific commit that was built.
A 'dev' centric community has very different requirements and priorities than a
'user' group !
warm regards
Saifi.
