On 07/06/2019 07:21, Chris Johns wrote:
Should we have something working before we make any additions to the user
manual?
It was actually my idea to add this section right now. My experience is that
documentation which is planned at the end of the project is never written.
Great and I also encourage this happening as well as posting for review but I am
not sure about merging into the main repo until you have some of the other
pieces place. Also I am not suggesting the support needs to be a polished
finished package, it just needs some more time to mature a little.
Ok, what should be the modus operandi for this GSoC project? Work with
Github forks and occasionally merge patches to upstream?
For me it is important to have the current state available somewhere. I
don't want to work with content spread throughout e-mails and patches.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
