Hi, > Replies are inline. One general comment: I think we should have MAINTAINERS > and a MAINTAINER file.
It’s not encouraged, people can come and go on a project and it could encourage off list traffic. If you really want to know who’s working on something you can check out version control history. > That way if people have a problem, they know who to contact with questions. > Thoughts? It better that questions are sent to the dev list, where anyone can help, not to individuals. > When we do release packaging, the way I was thinking about it (and apologies, > I was going to send a longer mail but you beat me to it) was: > > - we branch the git repo at a specific version (larva & newt) -- > rel_v0_0_8-b1 for example. > > - newt's built in package manager knows to fetch packages from that git > branch (we make the changes to newt once we branch.) May be an issue with this (I think not 100% sure), does that imply that a release can basically change over time? Or that it would be downloading un-released software? For something to be a release it must be voted on and while in incubation also voted on by the incubator PMC. So as long at that git branch only contained approved software that would be fine. > - We build newt for all supported platforms (Linux, Mac OS X, Windows) -- and > we distribute that, along with necessary LICENSE files on our website. Best to distribute via the apache mirrors, there a cgi script you can use to grab the artefacts from the nearest mirror. Not there must needs to be a source only release and an optional binary convenience release. > - Those eggs then come with individual LICENSE files, which have their > license info. Yep the LICENSE (and NOTICE) files need to reflect only what is bundled in the artefact downloaded. > They are Apache -- can you point me to the specific files you're referencing > so I can double check? ./hw/bsp/nrf51dk/include/bsp/cmsis_nvic.h ./hw/bsp/nrf52pdk/include/bsp/cmsis_nvic.h ./hw/bsp/olimex_stm32-e407_devboard/include/bsp/cmsis_nvic.h ./hw/bsp/stm32f3discovery/include/bsp/cmsis_nvic.h ./libs/cmsis-core/src/cmsis_nvic.c > Anyhow, here is the FatFs license, it is liberal Yep no issue there. > We can raise this with legal, alternatively we could move the MCU & BSP > definitions to github. People would need to config newt to point at the > github URL (newt add-clutch), but it would get around ASF license issues. Only if it’s considered an optional dependancy, but I think that is the case. i.e. It not required for newt/larva to work. We had similar issue with Adobe licensed software and Apache Flex. Thanks, Justin
