It all looks good to me Regards, Stan
On 2019/05/29 17:55:36, "Brian Spector" <[email protected]> wrote: > Hello, > > I’ve collated a set of near term objectives for the contributors and > those who want to be involved in Milagro going forward that we need to > achieve to get the project operational and start committing code. > > I would appreciate any feedback if you think I have missed any action > items. We can use this thread to collect them and then self-assign > tasks. > > *Reach out to ASF Infra* > 1. Open conversation with ASF #infra Slack. If they can give us the > things we need, then, assuming our requests our sound,... > 2. We need to open a JIRA ticket to request the provisioning of these > items below: > > > a) ASF Infra provisioned/approved Coveralls Account > b) ASF Infra provisioned/approved Travis/Jenkins/some CI account > connected to Milagro repositories. Currently, there is a non-sanction > Travis account connected to the repos. > c) Get INFRA to setup Confluence site for Milagro. I propose this be a > space devoted to publishing information for comment before it becomes > official by way of publishing on the milagro.apache.org site. > d) Remove irrelevant/out-of-date repos - assuming this operation is OK > within Apache best practices. > > - Separate To Do: Table discussion on dev about which repos are still > relevant and where the backlog of commits need to be placed into which > repository. I will send a separate email tomorrow morning on this. > > NOTE: Please give me your approval or comments as soon as possible, > particularly with regard to point C. > > * incubator-milagro > * incubator-milagro-crypto > * incubator-milagro-crypto-c > * incubator-milagro-java > * incubator-milagro-javascript > * incubator-milagro-mfa-js-client > * incubator-milagro-mfa-js-lib > * incubator-milagro-mfa-sdk-android > * incubator-milagro-mfa-sdk-core > * incubator-milagro-mfa-sdk-ios > * incubator-milagro-mfa-sdk-wp > * incubator-milagro-mfa-server > * incubator-milagro-tls > > *Account Creation* > Get Jan or Nick Kew to setup new accounts for Chris Morris, assuming > there are no NO votes and he accepts ascension as a contributor. > > *Project Website* > > What we need to do is organize the milagro GitHub repo site so that we > have the ash-site-source folder along with an asf-site-source branch, or > dedicate a new repo as the project’s website. > > The folder and branch will contain the website according to these > guidelines: http://www.apache.org/dev/project-site.html > > See Apache MXNet Incubator Site as an example of how they have done it: > https://github.com/apache/incubator-mxnet-site. > - I believe PPMC have the ability to create a new repo here: > https://selfserve.apache.org > - A committer can check their access here: > https://gitbox.apache.org/setup/ > > Currently, the Milagro website is out of date and the files are hosted > in subversion. We need to migrate to the new githubpubsub system and > Jeckyll/Jenkins build system. Infra should be able to help with this. > > *Podling Report* > > I will create a new Podling report and file it by end of week, so it is > not tardy. I will expect that some new updates to milagro-crypto repo > will come in over the next few hours. This development activity, new > PPMC and new contributor are good first steps to re-establishing some > credibility with the Apache community and harnessing the good will that > Milagro has with IBM, JPM, NTT, etc. so we will hopefully get their > development efforts focused here and re-contributing back to Milagro > going forward. > > Please let me know your comments as soon as possible. > > Thanks > Brian >
