Re: Omission in vote summary email template

[Brian Enright]

No me does matter in fact, this is the opposite of the normal position,
call please and we can square this away tonight as I think all parties wish
to close out.

I physically can take much more and then we have serious issues facing us
which is no subject matter for comedy.

Thx

On Fri, 1 Mar 2019 at 23:12, Miguel Guardado  wrote:

> Nome importa nada nokiero recibir ningún mensaje ba
>
> El vie., 1 de mar. de 2019 4:10 PM, sebb  escribió:
>
> > On Fri, 1 Mar 2019 at 22:47, Craig Russell  wrote:
> >
> > > Hi Sebb,
> > >
> > > > On Feb 28, 2019, at 2:54 AM, sebb  wrote:
> > > >
> > > > On Thu, 28 Feb 2019 at 09:52, sebb  wrote:
> > > >>
> > > >> The section:
> > > >>
> > > >> https://community.apache.org/newcommitter.html#close-vote
> > > >>
> > > >> says to summarise the binding vote counts only.
> > > >>
> > > >> I think that is wrong on two counts:
> > > >> - non-binding votes should not be ignored
> > > >> - individual votes should be listed to make it easy to check if all
> > > >> votes have been included and to check binding status
> > > >
> > > > Ignore the parts about binding status, as such votes are held on the
> > > > private list and so are automatically binding (if that even makes
> > > > sense for committer votes).
> > >
> > > The way the page is worded, I agree that "Binding" should not be part
> of
> > the email summary.
> >
> > I've since realised that there may be people on the private mailing
> > list who are not PMC members (e.g. ASF members).
> > However 'binding' is probably the wrong word to use.
> >
> > > If this is changed via CMS, is there an automatic rebuild of the web
> > site?
> >
> > I don't know, but generally CMS sites are built automatically.
> > You still have to publish the site.
> >
> > > Craig
> > > >
> > > > But I still think it would be useful to list the votes along with the
> > summary.
> > > >
> > > >> Can we get this changed?
> > > >>
> > > >> Sebb.
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > > Craig L Russell
> > > Secretary, Apache Software Foundation
> > > c...@apache.org  http://db.apache.org/jdo <
> > http://db.apache.org/jdo>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: Omission in vote summary email template

[Miguel Guardado]

Nome importa nada nokiero recibir ningún mensaje ba

El vie., 1 de mar. de 2019 4:10 PM, sebb  escribió:

> On Fri, 1 Mar 2019 at 22:47, Craig Russell  wrote:
> >
> > Hi Sebb,
> >
> > > On Feb 28, 2019, at 2:54 AM, sebb  wrote:
> > >
> > > On Thu, 28 Feb 2019 at 09:52, sebb  wrote:
> > >>
> > >> The section:
> > >>
> > >> https://community.apache.org/newcommitter.html#close-vote
> > >>
> > >> says to summarise the binding vote counts only.
> > >>
> > >> I think that is wrong on two counts:
> > >> - non-binding votes should not be ignored
> > >> - individual votes should be listed to make it easy to check if all
> > >> votes have been included and to check binding status
> > >
> > > Ignore the parts about binding status, as such votes are held on the
> > > private list and so are automatically binding (if that even makes
> > > sense for committer votes).
> >
> > The way the page is worded, I agree that "Binding" should not be part of
> the email summary.
>
> I've since realised that there may be people on the private mailing
> list who are not PMC members (e.g. ASF members).
> However 'binding' is probably the wrong word to use.
>
> > If this is changed via CMS, is there an automatic rebuild of the web
> site?
>
> I don't know, but generally CMS sites are built automatically.
> You still have to publish the site.
>
> > Craig
> > >
> > > But I still think it would be useful to list the votes along with the
> summary.
> > >
> > >> Can we get this changed?
> > >>
> > >> Sebb.
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > c...@apache.org  http://db.apache.org/jdo <
> http://db.apache.org/jdo>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Omission in vote summary email template

[sebb]

On Fri, 1 Mar 2019 at 22:47, Craig Russell  wrote:
>
> Hi Sebb,
>
> > On Feb 28, 2019, at 2:54 AM, sebb  wrote:
> >
> > On Thu, 28 Feb 2019 at 09:52, sebb  wrote:
> >>
> >> The section:
> >>
> >> https://community.apache.org/newcommitter.html#close-vote
> >>
> >> says to summarise the binding vote counts only.
> >>
> >> I think that is wrong on two counts:
> >> - non-binding votes should not be ignored
> >> - individual votes should be listed to make it easy to check if all
> >> votes have been included and to check binding status
> >
> > Ignore the parts about binding status, as such votes are held on the
> > private list and so are automatically binding (if that even makes
> > sense for committer votes).
>
> The way the page is worded, I agree that "Binding" should not be part of the 
> email summary.

I've since realised that there may be people on the private mailing
list who are not PMC members (e.g. ASF members).
However 'binding' is probably the wrong word to use.

> If this is changed via CMS, is there an automatic rebuild of the web site?

I don't know, but generally CMS sites are built automatically.
You still have to publish the site.

> Craig
> >
> > But I still think it would be useful to list the votes along with the 
> > summary.
> >
> >> Can we get this changed?
> >>
> >> Sebb.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Omission in vote summary email template

[Brian Enright]

Hi Craig

Thanks for your update, I’m happy to accept and would relish the challenge
and look forward to building relationships, making friends.

All we need to enable this is M to acknowledge the possible by way of a
personal conversation.

I have no desire to engage with constraints and need to put this away
tonight and I have issues should it prolong any later which are having an
negative effort on my well being.

Thanks
Brian

On Fri, 1 Mar 2019 at 22:47, Craig Russell  wrote:

> Hi Sebb,
>
> > On Feb 28, 2019, at 2:54 AM, sebb  wrote:
> >
> > On Thu, 28 Feb 2019 at 09:52, sebb  wrote:
> >>
> >> The section:
> >>
> >> https://community.apache.org/newcommitter.html#close-vote
> >>
> >> says to summarise the binding vote counts only.
> >>
> >> I think that is wrong on two counts:
> >> - non-binding votes should not be ignored
> >> - individual votes should be listed to make it easy to check if all
> >> votes have been included and to check binding status
> >
> > Ignore the parts about binding status, as such votes are held on the
> > private list and so are automatically binding (if that even makes
> > sense for committer votes).
>
> The way the page is worded, I agree that "Binding" should not be part of
> the email summary.
>
> If this is changed via CMS, is there an automatic rebuild of the web site?
>
> Craig
> >
> > But I still think it would be useful to list the votes along with the
> summary.
> >
> >> Can we get this changed?
> >>
> >> Sebb.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo <
> http://db.apache.org/jdo>
>

Re: Omission in vote summary email template

[Craig Russell]

Hi Sebb,

> On Feb 28, 2019, at 2:54 AM, sebb  wrote:
> 
> On Thu, 28 Feb 2019 at 09:52, sebb  wrote:
>> 
>> The section:
>> 
>> https://community.apache.org/newcommitter.html#close-vote
>> 
>> says to summarise the binding vote counts only.
>> 
>> I think that is wrong on two counts:
>> - non-binding votes should not be ignored
>> - individual votes should be listed to make it easy to check if all
>> votes have been included and to check binding status
> 
> Ignore the parts about binding status, as such votes are held on the
> private list and so are automatically binding (if that even makes
> sense for committer votes).

The way the page is worded, I agree that "Binding" should not be part of the 
email summary.

If this is changed via CMS, is there an automatic rebuild of the web site?

Craig
> 
> But I still think it would be useful to list the votes along with the summary.
> 
>> Can we get this changed?
>> 
>> Sebb.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org  http://db.apache.org/jdo 

[jira] [Commented] (COMDEV-306) GSoC - Allura - Convert to python 3

[Dave Brondsema (JIRA)]

[ 
https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782126#comment-16782126
 ] 

Dave Brondsema commented on COMDEV-306:
---

[~Abhism] you should join the dev mailing list at 
[https://lists.apache.org/list.html?d...@allura.apache.org] and introduce 
yourself.  That's the best place to ask questions about Allura.  I would 
recommend first installing Allura and getting it running so you can be familiar 
with it.  Then you could try upgrading one dependency from requirements.txt at 
a time, and see if everything works and tests pass still.  That'd be a good 
starting task to try.

> GSoC - Allura - Convert to python 3
> ---
>
> Key: COMDEV-306
> URL: https://issues.apache.org/jira/browse/COMDEV-306
> Project: Community Development
>  Issue Type: Improvement
>  Components: GSoC/Mentoring ideas
>Reporter: Dave Brondsema
>Priority: Major
>  Labels: gsoc2019, python
>
> Allura is a large mature codebase, and relies on many dependencies.  The path 
> to python 3 will have many steps, but we need to start working on it.  GSOC 
> work would include familiarizing with porting guides like 
> [https://docs.python.org/3/howto/pyporting.html] and 
> [https://portingguide.readthedocs.io/en/latest/] and 
> [http://python3porting.com/] and then working through steps like:
>  * upgrading dependencies, and updating code & tests to match
>  * removing or replacing dependencies where needed, and updating code
>  * running futurize or modernize, manual code changes where needed, cleanup, 
> etc
>  * testing
>  * documentation updates
>  * Docker updates
>  * more, probably :)
> https://allura.apache.org/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Logo design using Apache licence 2.0 fonts

[Romen Sroff]

On 2/24/19, Shane Curcuru  wrote:
> Ivana Soldic wrote on 2/22/19 1:20 PM:
>> Hello,
>> I would like to use fonts covered by your Apache Licence 2.0 in logo
>> designs, not as fonts itself, but converted to curves. I have read Apache
>> Licence 2.0 but I'm not sure how this applies to logo design. Logos would
>> be for a commercial purpose and I plan to sell them. Can you tell me do I
>> have some obligations in that case to the Apache? Please answer as simple
>> as you can since English is not my first language. Feel free to ask if
>> you
>> have some questions.
>
> First off, thank you for carefully reading and respecting the license!
>
> The important question is: who's font is it?  Many companies use our
> license for their software, and it's up to the company you got the font
> from to provide any legal answer to your question.  You do not have any
> obligations to the ASF or us, since we didn't create the font.
>
> We are all volunteers here on this mailing list - not paid - and we
> can't give you legal advice; you'd need to ask a lawyer for specific
> feedback on what your commercial company can do with these fonts.
>
> However, I can say that I have seen a number of other logo designers
> using Apache licensed fonts as part of their logo designs.  I'm not
> personally aware of any legal or commercial issues that the logo
> designers faced from their work.  So in most cases I've seen, you don't
> have anything to worry about.
>
> Does that help?
>
> --
>
> - Shane
>   ASF Member
>   The Apache Software Foundation
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Commented] (COMDEV-306) GSoC - Allura - Convert to python 3

[Abhishek Chaudhary (JIRA)]

[ 
https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781754#comment-16781754
 ] 

Abhishek Chaudhary commented on COMDEV-306:
---

[~brondsem] I would like to work on this project. Can you tell me from where 
should i began ?

> GSoC - Allura - Convert to python 3
> ---
>
> Key: COMDEV-306
> URL: https://issues.apache.org/jira/browse/COMDEV-306
> Project: Community Development
>  Issue Type: Improvement
>  Components: GSoC/Mentoring ideas
>Reporter: Dave Brondsema
>Priority: Major
>  Labels: gsoc2019, python
>
> Allura is a large mature codebase, and relies on many dependencies.  The path 
> to python 3 will have many steps, but we need to start working on it.  GSOC 
> work would include familiarizing with porting guides like 
> [https://docs.python.org/3/howto/pyporting.html] and 
> [https://portingguide.readthedocs.io/en/latest/] and 
> [http://python3porting.com/] and then working through steps like:
>  * upgrading dependencies, and updating code & tests to match
>  * removing or replacing dependencies where needed, and updating code
>  * running futurize or modernize, manual code changes where needed, cleanup, 
> etc
>  * testing
>  * documentation updates
>  * Docker updates
>  * more, probably :)
> https://allura.apache.org/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org