Re: dev Digest of: get.107_109

[Justin Mclean]

Hi,

 1. we do have a hangout to discuss the project every 2 weeks.   Is this not 
 appropriate?

There’s nothing wrong with that and if fact I would assume that helps build 
community. It would certailly help if the minutes/summary are posted to the 
mailing list, in plain text preferably, posting to a doc may mean that 
eventually that information is lost and preferably in the same thread. That way 
people new to the project or those not involved in the meetup can look at the 
email archives and get a better idea to what is going on. Any decisions however 
need to made on the mailing list. [1]

Thanks,
Justin

1. http://www.apache.org/dev/pmc.html#mailing-list-naming-policy

Re: [VOTE] Release Apache Myriad 0.1.0 (incubating)

[Justin Mclean]

Hi,

> We need to fix the LICENSE, exclude the gradle-wrapper.jar from the
> tarball, and add build instructions (potentially also on how to download
> gradle as well) in the README.

IMO The jar would be the only blocking issue, but if you’re making another RC 
then you might as well fix the rest.

Thanks,
Justin

Re: [VOTE] Release Apache Myriad 0.1.0 (incubating)

[Justin Mclean]

Hi,

>  I've a few questions to ask regarding the update to LICENSE. I'll ask
> them on the general@ thread.

Ask away. Also happy to review it before it get to the incubator if you want.

Thanks,
Justin

Re: [VOTE] Release Apache Myriad 0.1.0 (incubating)

[Justin Mclean]

Hi,

> (This may be a question for Jim Klucar (Myriad's UI developer), but if you
> are familiar with bootstrap's licensing, your guidance is much appreciated.)

Different versions of bootstrap have had different licenses you need to respect 
the version you have bundled not the current license.

> Also, the bootstrap-myriad.css[1] file mentions normalize.css as MIT
> licensed.

Looks MIT to me compare [1] with [2]. The principal here is [3].

Thanks,
Justin

1. https://github.com/necolas/normalize.css/blob/master/LICENSE.md 

2. https://opensource.org/licenses/MIT 
3. http://www.apache.org/dev/licensing-howto.html#guiding-principle 

Re: [VOTE] Release Apache Myriad 0.1.0 (incubating)

[Justin Mclean]

Hi,

> I didn't understand what's not correct in the appendix part of the LICENSE.
> I compared the appendix section with that from the stock, and couldn't spot
> a difference. Can you please clarify?

Yep the text should be this:
   Copyright [] [name of copyright owner]

Not this:
  Copyright 2012-present Apache Software Foundation

Just replace the whole file with the official version here [1].

Thanks,
Justin

1. http://www.apache.org/licenses/LICENSE-2.0.txt

Re: [VOTE] Release Apache Myriad 0.1.0 (incubating)

[Justin Mclean]

Hi,

> @Justin - it'll be great if you can review the PR as well. Thanks!
> 
> [1] https://github.com/apache/incubator-myriad/pull/49 
> 
Looks good to me.

Thanks,
Justin

Re: [Vote] Release apache-myriad-0.2.0-incubating (release candidate 1)

[Justin Mclean]

Hi,

As I mistakenly thought this was an incubator release I went ahead and reviewed 
it. If this vote passes you get my +1 on the IPMC list as well.

+1 (binding) Can you fix the year in the next release.

I checked:
- incubating in name
- signature and hashes correct
- DISCLAIMER exists
- LICENSE is good
- NOTICE has incorrect year
- No unexpected binaries in the source release
- Can compile from source

Thanks,
Justin

Re: [Vote] Release apache-myriad-0.2.0-incubating (release candidate 1)

[Justin Mclean]

Hi,
Can you include a link to results of the vote on the dev list.
Thanks,
Justin

Re: Please do not retire Myriad

[Justin Mclean]

Hi,

> 1. Try to convince to Apache managers (I don't now the correct term)
> for an exception to allow you accept commits from external
> contributors (like me).

All and any contributions are welcome, that is not he issue here. The board 
requires oversight of at least 3 (P)PMC members. For incubating project 
generally the committers are the PPMC.

> 2. Follow your first proposal, create a new github organization, for
> example (github.com/myriad) and working there.

As the software is under the Apache license anyone can do this, you don't need 
to ask for permission.

> Maybe in the future we can try go to Apache incubation again.

And I’m sure the Apache incubator would welcome that.

> I guess we are three people with interest into continue the project,
> you, Juan P. and myself. From my side I am working in a local fork for
> enhancing some stuff.

Alternatively if the people above have contributed and promoted the project 
(I’m sorry but I don’t know the full history here) and the currenrt PPMC 
recognise that and votes you in as PPMC members then that may be enough to 
continue the project at Apache.

Thanks.
Justin

Re: Please do not retire Myriad

[Justin Mclean]

Hi,

> Unfortunately I don't have permissions for updating the report.

It possible to email the report in and/or ask for someone to submit it for you.

It’s unclear to me why you seem to be duplicating the site and mailing list if 
you want to keep the project at Apache. Decisions and communication needs to be 
happening on this list and you need to use Apache infrastructure for the site. 
I'm not sure trademarks would look too fondly on the site being hosted at 
http://www.myriad-framework.org.  Either you want the project to stay at Apache 
or you are forking it. If you are forking it then your project is not an Apache 
incubating project and that site (including probably the domain name) 
http://www.myriad-framework.org would need some work to comply with ASF policy 
on branding and trademarks. [1]

> The other option is to change the incubator ownership to interested
> people like some of us.

Are your project mentors still active? They may be able to help here. Ownership 
cannot just be handed over but they (and any other active PMC member) could 
vote new PMC members in.

Thanks,
Justin

1. https://www.apache.org/foundation/marks/domains.html

Podling Report Reminder - September 2018

[Justin Mclean]

Hi,
The incubator PMC would appreciated if you could complete the podling report on 
time. It takes time to prepare the incubator report, have your mentors sign off 
the report and for the board to review it, in order for all that to happen the 
report is due in the next two days.
Thanks,
Justin

Re: Podling Report Reminder - September 2018

[Justin Mclean]

Hi,

Sorry please ignore this, it was sent in error.

Thanks,
Justin

Incubator Podling Report (Due 5th December)

[Justin Mclean]

Hi,

The incubator PMC would appreciated if you could complete the podling report on 
time it's due on 5th December in a few days. It takes time to prepare the 
incubator report, have your mentors sign off the report and for the board to 
review it, so it's best if you can get it in early.

Thanks,
Justin

Re: Podling Report Reminder - September 2019

[Justin Mclean]

Hi,

Thanks for submitting the reports, but unless it is improved, it's going to be 
rejected and I'll ask for you to report next month. The item listed under 
graduation have nothing to do with graduation. The issues should be about 
moving towards doing things how Apache project work and community, not 
functionality. I's also like to see some more detail and less stats, it 
doesn't;t really matter how many twitter followers you have and that number on 
it own doesn't tell anyone outside the project about community growth.

Thanks,
Justin

Re: Podling Report Reminder - September 2019

[Justin Mclean]

Hi,

> Do we have the opportunity of improving right now, or we are out of time?

You can improve it now.

Thanks,
Justin