[Proposal] Extend the ack section of the Release Notes

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

[Proposal] Extend the ack section of the Release Notes

vmassol
Administrator
Hi devs,

Right now we’ve started acknowledging the committers in the Release notes.

I’d like to propose to extend that try to ack everyone who participates in one way or another to a release, and not just developers.

I can think of 3 more items to add:

A) All the JIRA issue reporters that have had an issue fixed for the release (bug, improvement, new feature, etc). They took the time to report an issue and thus they’ve helped the committers to improve the quality of the release and thus they should be acknowledged. This allows us to also ack QA. We could decide to exclude the reporters who’ve also been committers or leave them in.

B) The people who’ve contributed translations done after the start of the release development.

Ideally we would also ack:

C) The people who’ve helped on the list for the release
D) The people who’ve helped on the Design and made proposals that made it to the release. I’m thinking of Caty for example. Luckily Caty also commits some code and often she’s recognised through commits.

The problem with C) and D) is that they’re hard to gather. But we could do it on an ad-hoc basis by adding them to the RN during the development (when they help) instead of doing it at the end.

In any case I’d like to focus on A) and B) FTM and I’m proposing to add them to the Release Plan since they’re easy to find out.

WDYT?

Thanks
-Vincent

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

vmassol
Administrator

> On 5 Feb 2017, at 11:07, Vincent Massol <[hidden email]> wrote:
>
> Hi devs,
>
> Right now we’ve started acknowledging the committers in the Release notes.
>
> I’d like to propose to extend that try to ack everyone who participates in one way or another to a release, and not just developers.
>
> I can think of 3 more items to add:

s/3/a few

> A) All the JIRA issue reporters that have had an issue fixed for the release (bug, improvement, new feature, etc). They took the time to report an issue and thus they’ve helped the committers to improve the quality of the release and thus they should be acknowledged. This allows us to also ack QA. We could decide to exclude the reporters who’ve also been committers or leave them in.
>
> B) The people who’ve contributed translations done after the start of the release development.
>
> Ideally we would also ack:
>
> C) The people who’ve helped on the list for the release
> D) The people who’ve helped on the Design and made proposals that made it to the release. I’m thinking of Caty for example. Luckily Caty also commits some code and often she’s recognised through commits.

E) People helping having improved xwiki.org by contributing doc. We would need tor remove people who modified pages by scripts (such as scheduler jobs).

Maybe E) is not that hard to do and could be included now.

WDYT?

Thanks
-Vincent

> The problem with C) and D) is that they’re hard to gather. But we could do it on an ad-hoc basis by adding them to the RN during the development (when they help) instead of doing it at the end.
>
> In any case I’d like to focus on A) and B) FTM and I’m proposing to add them to the Release Plan since they’re easy to find out.
>
> WDYT?
>
> Thanks
> -Vincent
>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Marius Dumitru Florea
In reply to this post by vmassol
+1

Thanks,
Marius

On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:

> Hi devs,
>
> Right now we’ve started acknowledging the committers in the Release notes.
>
> I’d like to propose to extend that try to ack everyone who participates in
> one way or another to a release, and not just developers.
>
> I can think of 3 more items to add:
>
> A) All the JIRA issue reporters that have had an issue fixed for the
> release (bug, improvement, new feature, etc). They took the time to report
> an issue and thus they’ve helped the committers to improve the quality of
> the release and thus they should be acknowledged. This allows us to also
> ack QA. We could decide to exclude the reporters who’ve also been
> committers or leave them in.
>
> B) The people who’ve contributed translations done after the start of the
> release development.
>
> Ideally we would also ack:
>
> C) The people who’ve helped on the list for the release
> D) The people who’ve helped on the Design and made proposals that made it
> to the release. I’m thinking of Caty for example. Luckily Caty also commits
> some code and often she’s recognised through commits.
>
> The problem with C) and D) is that they’re hard to gather. But we could do
> it on an ad-hoc basis by adding them to the RN during the development (when
> they help) instead of doing it at the end.
>
> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
> them to the Release Plan since they’re easy to find out.
>
> WDYT?
>
> Thanks
> -Vincent
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Thomas Mortagne
Administrator
+1 for adding any source of contributions as long as it's automated or
close to automated (like executing one command/request and
copy/pasting the result)

On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
<[hidden email]> wrote:

> +1
>
> Thanks,
> Marius
>
> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:
>
>> Hi devs,
>>
>> Right now we’ve started acknowledging the committers in the Release notes.
>>
>> I’d like to propose to extend that try to ack everyone who participates in
>> one way or another to a release, and not just developers.
>>
>> I can think of 3 more items to add:
>>
>> A) All the JIRA issue reporters that have had an issue fixed for the
>> release (bug, improvement, new feature, etc). They took the time to report
>> an issue and thus they’ve helped the committers to improve the quality of
>> the release and thus they should be acknowledged. This allows us to also
>> ack QA. We could decide to exclude the reporters who’ve also been
>> committers or leave them in.
>>
>> B) The people who’ve contributed translations done after the start of the
>> release development.
>>
>> Ideally we would also ack:
>>
>> C) The people who’ve helped on the list for the release
>> D) The people who’ve helped on the Design and made proposals that made it
>> to the release. I’m thinking of Caty for example. Luckily Caty also commits
>> some code and often she’s recognised through commits.
>>
>> The problem with C) and D) is that they’re hard to gather. But we could do
>> it on an ad-hoc basis by adding them to the RN during the development (when
>> they help) instead of doing it at the end.
>>
>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
>> them to the Release Plan since they’re easy to find out.
>>
>> WDYT?
>>
>> Thanks
>> -Vincent
>>
>>



--
Thomas Mortagne
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Alexandru Cotiuga
+1

Thanks,
Alex

On Mon, Feb 6, 2017 at 11:39 AM, Thomas Mortagne <[hidden email]>
wrote:

> +1 for adding any source of contributions as long as it's automated or
> close to automated (like executing one command/request and
> copy/pasting the result)
>
> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
> <[hidden email]> wrote:
> > +1
> >
> > Thanks,
> > Marius
> >
> > On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]>
> wrote:
> >
> >> Hi devs,
> >>
> >> Right now we’ve started acknowledging the committers in the Release
> notes.
> >>
> >> I’d like to propose to extend that try to ack everyone who participates
> in
> >> one way or another to a release, and not just developers.
> >>
> >> I can think of 3 more items to add:
> >>
> >> A) All the JIRA issue reporters that have had an issue fixed for the
> >> release (bug, improvement, new feature, etc). They took the time to
> report
> >> an issue and thus they’ve helped the committers to improve the quality
> of
> >> the release and thus they should be acknowledged. This allows us to also
> >> ack QA. We could decide to exclude the reporters who’ve also been
> >> committers or leave them in.
> >>
> >> B) The people who’ve contributed translations done after the start of
> the
> >> release development.
> >>
> >> Ideally we would also ack:
> >>
> >> C) The people who’ve helped on the list for the release
> >> D) The people who’ve helped on the Design and made proposals that made
> it
> >> to the release. I’m thinking of Caty for example. Luckily Caty also
> commits
> >> some code and often she’s recognised through commits.
> >>
> >> The problem with C) and D) is that they’re hard to gather. But we could
> do
> >> it on an ad-hoc basis by adding them to the RN during the development
> (when
> >> they help) instead of doing it at the end.
> >>
> >> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
> >> them to the Release Plan since they’re easy to find out.
> >>
> >> WDYT?
> >>
> >> Thanks
> >> -Vincent
> >>
> >>
>
>
>
> --
> Thomas Mortagne
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Sergiu Dumitriu-3
In reply to this post by Thomas Mortagne
Same as Thomas.

On 02/06/2017 04:39 AM, Thomas Mortagne wrote:

> +1 for adding any source of contributions as long as it's automated or
> close to automated (like executing one command/request and
> copy/pasting the result)
>
> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
> <[hidden email]> wrote:
>> +1
>>
>> Thanks,
>> Marius
>>
>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:
>>
>>> Hi devs,
>>>
>>> Right now we’ve started acknowledging the committers in the Release notes.
>>>
>>> I’d like to propose to extend that try to ack everyone who participates in
>>> one way or another to a release, and not just developers.
>>>
>>> I can think of 3 more items to add:
>>>
>>> A) All the JIRA issue reporters that have had an issue fixed for the
>>> release (bug, improvement, new feature, etc). They took the time to report
>>> an issue and thus they’ve helped the committers to improve the quality of
>>> the release and thus they should be acknowledged. This allows us to also
>>> ack QA. We could decide to exclude the reporters who’ve also been
>>> committers or leave them in.
>>>
>>> B) The people who’ve contributed translations done after the start of the
>>> release development.
>>>
>>> Ideally we would also ack:
>>>
>>> C) The people who’ve helped on the list for the release
>>> D) The people who’ve helped on the Design and made proposals that made it
>>> to the release. I’m thinking of Caty for example. Luckily Caty also commits
>>> some code and often she’s recognised through commits.
>>>
>>> The problem with C) and D) is that they’re hard to gather. But we could do
>>> it on an ad-hoc basis by adding them to the RN during the development (when
>>> they help) instead of doing it at the end.
>>>
>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
>>> them to the Release Plan since they’re easy to find out.
>>>
>>> WDYT?
>>>
>>> Thanks
>>> -Vincent
>>>
>>>
>
>
>


--
Sergiu Dumitriu
http://purl.org/net/sergiu
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Guillaume Delhumeau
Same as Thomas too.

2017-02-06 16:13 GMT+01:00 Sergiu Dumitriu <[hidden email]>:

> Same as Thomas.
>
> On 02/06/2017 04:39 AM, Thomas Mortagne wrote:
> > +1 for adding any source of contributions as long as it's automated or
> > close to automated (like executing one command/request and
> > copy/pasting the result)
> >
> > On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
> > <[hidden email]> wrote:
> >> +1
> >>
> >> Thanks,
> >> Marius
> >>
> >> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]>
> wrote:
> >>
> >>> Hi devs,
> >>>
> >>> Right now we’ve started acknowledging the committers in the Release
> notes.
> >>>
> >>> I’d like to propose to extend that try to ack everyone who
> participates in
> >>> one way or another to a release, and not just developers.
> >>>
> >>> I can think of 3 more items to add:
> >>>
> >>> A) All the JIRA issue reporters that have had an issue fixed for the
> >>> release (bug, improvement, new feature, etc). They took the time to
> report
> >>> an issue and thus they’ve helped the committers to improve the quality
> of
> >>> the release and thus they should be acknowledged. This allows us to
> also
> >>> ack QA. We could decide to exclude the reporters who’ve also been
> >>> committers or leave them in.
> >>>
> >>> B) The people who’ve contributed translations done after the start of
> the
> >>> release development.
> >>>
> >>> Ideally we would also ack:
> >>>
> >>> C) The people who’ve helped on the list for the release
> >>> D) The people who’ve helped on the Design and made proposals that made
> it
> >>> to the release. I’m thinking of Caty for example. Luckily Caty also
> commits
> >>> some code and often she’s recognised through commits.
> >>>
> >>> The problem with C) and D) is that they’re hard to gather. But we
> could do
> >>> it on an ad-hoc basis by adding them to the RN during the development
> (when
> >>> they help) instead of doing it at the end.
> >>>
> >>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
> >>> them to the Release Plan since they’re easy to find out.
> >>>
> >>> WDYT?
> >>>
> >>> Thanks
> >>> -Vincent
> >>>
> >>>
> >
> >
> >
>
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu
>



--
Guillaume Delhumeau ([hidden email])
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

vmassol
Administrator
In reply to this post by vmassol

> On 5 Feb 2017, at 11:07, Vincent Massol <[hidden email]> wrote:
>
> Hi devs,
>
> Right now we’ve started acknowledging the committers in the Release notes.
>
> I’d like to propose to extend that try to ack everyone who participates in one way or another to a release, and not just developers.
>
> I can think of 3 more items to add:
>
> A) All the JIRA issue reporters that have had an issue fixed for the release (bug, improvement, new feature, etc). They took the time to report an issue and thus they’ve helped the committers to improve the quality of the release and thus they should be acknowledged. This allows us to also ack QA. We could decide to exclude the reporters who’ve also been committers or leave them in.

Here’s how to automate this:

{{groovy}}
def jql = URLEncoder.encode('category = "Top Level Projects" AND (fixVersion = "9.0-rc-1" OR fixVersion = "9.0") AND resolution = Fixed AND component != "Development Issues only"', "UTF-8")
def columns = "field=reporter"

def url = "http://jira.xwiki.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=${jql}&${columns}".toURL().text
def root = new XmlSlurper().parseText(url)

def reporters = [] as TreeSet
root.channel.item.each() {
  reporters.add(it.reporter.toString())
}

println "{{{"
reporters.each() {
  println "* ${it}"
}
println "}}}"
{{/groovy}}

Thanks
-Vincent

>
> B) The people who’ve contributed translations done after the start of the release development.
>
> Ideally we would also ack:
>
> C) The people who’ve helped on the list for the release
> D) The people who’ve helped on the Design and made proposals that made it to the release. I’m thinking of Caty for example. Luckily Caty also commits some code and often she’s recognised through commits.
>
> The problem with C) and D) is that they’re hard to gather. But we could do it on an ad-hoc basis by adding them to the RN during the development (when they help) instead of doing it at the end.
>
> In any case I’d like to focus on A) and B) FTM and I’m proposing to add them to the Release Plan since they’re easy to find out.
>
> WDYT?
>
> Thanks
> -Vincent
>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

vmassol
Administrator
In reply to this post by Thomas Mortagne

> On 6 Feb 2017, at 10:39, Thomas Mortagne <[hidden email]> wrote:
>
> +1 for adding any source of contributions as long as it's automated or
> close to automated (like executing one command/request and
> copy/pasting the result)

@Thomas: Could I let you write some script to generate:
"B) The people who’ve contributed translations done after the start of the release development.”

?

:)

So the idea is to give a start and end date and get the list of translators during that period.

Thanks
-Vincent

> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
> <[hidden email]> wrote:
>> +1
>>
>> Thanks,
>> Marius
>>
>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:
>>
>>> Hi devs,
>>>
>>> Right now we’ve started acknowledging the committers in the Release notes.
>>>
>>> I’d like to propose to extend that try to ack everyone who participates in
>>> one way or another to a release, and not just developers.
>>>
>>> I can think of 3 more items to add:
>>>
>>> A) All the JIRA issue reporters that have had an issue fixed for the
>>> release (bug, improvement, new feature, etc). They took the time to report
>>> an issue and thus they’ve helped the committers to improve the quality of
>>> the release and thus they should be acknowledged. This allows us to also
>>> ack QA. We could decide to exclude the reporters who’ve also been
>>> committers or leave them in.
>>>
>>> B) The people who’ve contributed translations done after the start of the
>>> release development.
>>>
>>> Ideally we would also ack:
>>>
>>> C) The people who’ve helped on the list for the release
>>> D) The people who’ve helped on the Design and made proposals that made it
>>> to the release. I’m thinking of Caty for example. Luckily Caty also commits
>>> some code and often she’s recognised through commits.
>>>
>>> The problem with C) and D) is that they’re hard to gather. But we could do
>>> it on an ad-hoc basis by adding them to the RN during the development (when
>>> they help) instead of doing it at the end.
>>>
>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
>>> them to the Release Plan since they’re easy to find out.
>>>
>>> WDYT?
>>>
>>> Thanks
>>> -Vincent
>>>
>>>
>
>
>
> --
> Thomas Mortagne

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Thomas Mortagne
Administrator
Already exist: http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?lowerBound=201601201&upperBound=20170106

What is missing is find out the dates to pass as parameters.

On Mon, Feb 6, 2017 at 5:33 PM, Vincent Massol <[hidden email]> wrote:

>
>> On 6 Feb 2017, at 10:39, Thomas Mortagne <[hidden email]> wrote:
>>
>> +1 for adding any source of contributions as long as it's automated or
>> close to automated (like executing one command/request and
>> copy/pasting the result)
>
> @Thomas: Could I let you write some script to generate:
> "B) The people who’ve contributed translations done after the start of the release development.”
>
> ?
>
> :)
>
> So the idea is to give a start and end date and get the list of translators during that period.
>
> Thanks
> -Vincent
>
>> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
>> <[hidden email]> wrote:
>>> +1
>>>
>>> Thanks,
>>> Marius
>>>
>>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:
>>>
>>>> Hi devs,
>>>>
>>>> Right now we’ve started acknowledging the committers in the Release notes.
>>>>
>>>> I’d like to propose to extend that try to ack everyone who participates in
>>>> one way or another to a release, and not just developers.
>>>>
>>>> I can think of 3 more items to add:
>>>>
>>>> A) All the JIRA issue reporters that have had an issue fixed for the
>>>> release (bug, improvement, new feature, etc). They took the time to report
>>>> an issue and thus they’ve helped the committers to improve the quality of
>>>> the release and thus they should be acknowledged. This allows us to also
>>>> ack QA. We could decide to exclude the reporters who’ve also been
>>>> committers or leave them in.
>>>>
>>>> B) The people who’ve contributed translations done after the start of the
>>>> release development.
>>>>
>>>> Ideally we would also ack:
>>>>
>>>> C) The people who’ve helped on the list for the release
>>>> D) The people who’ve helped on the Design and made proposals that made it
>>>> to the release. I’m thinking of Caty for example. Luckily Caty also commits
>>>> some code and often she’s recognised through commits.
>>>>
>>>> The problem with C) and D) is that they’re hard to gather. But we could do
>>>> it on an ad-hoc basis by adding them to the RN during the development (when
>>>> they help) instead of doing it at the end.
>>>>
>>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
>>>> them to the Release Plan since they’re easy to find out.
>>>>
>>>> WDYT?
>>>>
>>>> Thanks
>>>> -Vincent
>>>>
>>>>
>>
>>
>>
>> --
>> Thomas Mortagne
>



--
Thomas Mortagne
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Thomas Mortagne
Administrator
There is a typo in the previous URL:
http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?lowerBound=20161201&upperBound=20170106

I'm surprised $datetool.toDate does not complain about a weird date
like "201601201".

On Mon, Feb 6, 2017 at 8:35 PM, Thomas Mortagne
<[hidden email]> wrote:

> Already exist: http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?lowerBound=201601201&upperBound=20170106
>
> What is missing is find out the dates to pass as parameters.
>
> On Mon, Feb 6, 2017 at 5:33 PM, Vincent Massol <[hidden email]> wrote:
>>
>>> On 6 Feb 2017, at 10:39, Thomas Mortagne <[hidden email]> wrote:
>>>
>>> +1 for adding any source of contributions as long as it's automated or
>>> close to automated (like executing one command/request and
>>> copy/pasting the result)
>>
>> @Thomas: Could I let you write some script to generate:
>> "B) The people who’ve contributed translations done after the start of the release development.”
>>
>> ?
>>
>> :)
>>
>> So the idea is to give a start and end date and get the list of translators during that period.
>>
>> Thanks
>> -Vincent
>>
>>> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
>>> <[hidden email]> wrote:
>>>> +1
>>>>
>>>> Thanks,
>>>> Marius
>>>>
>>>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:
>>>>
>>>>> Hi devs,
>>>>>
>>>>> Right now we’ve started acknowledging the committers in the Release notes.
>>>>>
>>>>> I’d like to propose to extend that try to ack everyone who participates in
>>>>> one way or another to a release, and not just developers.
>>>>>
>>>>> I can think of 3 more items to add:
>>>>>
>>>>> A) All the JIRA issue reporters that have had an issue fixed for the
>>>>> release (bug, improvement, new feature, etc). They took the time to report
>>>>> an issue and thus they’ve helped the committers to improve the quality of
>>>>> the release and thus they should be acknowledged. This allows us to also
>>>>> ack QA. We could decide to exclude the reporters who’ve also been
>>>>> committers or leave them in.
>>>>>
>>>>> B) The people who’ve contributed translations done after the start of the
>>>>> release development.
>>>>>
>>>>> Ideally we would also ack:
>>>>>
>>>>> C) The people who’ve helped on the list for the release
>>>>> D) The people who’ve helped on the Design and made proposals that made it
>>>>> to the release. I’m thinking of Caty for example. Luckily Caty also commits
>>>>> some code and often she’s recognised through commits.
>>>>>
>>>>> The problem with C) and D) is that they’re hard to gather. But we could do
>>>>> it on an ad-hoc basis by adding them to the RN during the development (when
>>>>> they help) instead of doing it at the end.
>>>>>
>>>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
>>>>> them to the Release Plan since they’re easy to find out.
>>>>>
>>>>> WDYT?
>>>>>
>>>>> Thanks
>>>>> -Vincent
>>>>>
>>>>>
>>>
>>>
>>>
>>> --
>>> Thomas Mortagne
>>
>
>
>
> --
> Thomas Mortagne



--
Thomas Mortagne
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Thomas Mortagne
Administrator
(This is all modifications made to documents containing a translation object)


On Mon, Feb 6, 2017 at 8:45 PM, Thomas Mortagne
<[hidden email]> wrote:

> There is a typo in the previous URL:
> http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?lowerBound=20161201&upperBound=20170106
>
> I'm surprised $datetool.toDate does not complain about a weird date
> like "201601201".
>
> On Mon, Feb 6, 2017 at 8:35 PM, Thomas Mortagne
> <[hidden email]> wrote:
>> Already exist: http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?lowerBound=201601201&upperBound=20170106
>>
>> What is missing is find out the dates to pass as parameters.
>>
>> On Mon, Feb 6, 2017 at 5:33 PM, Vincent Massol <[hidden email]> wrote:
>>>
>>>> On 6 Feb 2017, at 10:39, Thomas Mortagne <[hidden email]> wrote:
>>>>
>>>> +1 for adding any source of contributions as long as it's automated or
>>>> close to automated (like executing one command/request and
>>>> copy/pasting the result)
>>>
>>> @Thomas: Could I let you write some script to generate:
>>> "B) The people who’ve contributed translations done after the start of the release development.”
>>>
>>> ?
>>>
>>> :)
>>>
>>> So the idea is to give a start and end date and get the list of translators during that period.
>>>
>>> Thanks
>>> -Vincent
>>>
>>>> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
>>>> <[hidden email]> wrote:
>>>>> +1
>>>>>
>>>>> Thanks,
>>>>> Marius
>>>>>
>>>>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]> wrote:
>>>>>
>>>>>> Hi devs,
>>>>>>
>>>>>> Right now we’ve started acknowledging the committers in the Release notes.
>>>>>>
>>>>>> I’d like to propose to extend that try to ack everyone who participates in
>>>>>> one way or another to a release, and not just developers.
>>>>>>
>>>>>> I can think of 3 more items to add:
>>>>>>
>>>>>> A) All the JIRA issue reporters that have had an issue fixed for the
>>>>>> release (bug, improvement, new feature, etc). They took the time to report
>>>>>> an issue and thus they’ve helped the committers to improve the quality of
>>>>>> the release and thus they should be acknowledged. This allows us to also
>>>>>> ack QA. We could decide to exclude the reporters who’ve also been
>>>>>> committers or leave them in.
>>>>>>
>>>>>> B) The people who’ve contributed translations done after the start of the
>>>>>> release development.
>>>>>>
>>>>>> Ideally we would also ack:
>>>>>>
>>>>>> C) The people who’ve helped on the list for the release
>>>>>> D) The people who’ve helped on the Design and made proposals that made it
>>>>>> to the release. I’m thinking of Caty for example. Luckily Caty also commits
>>>>>> some code and often she’s recognised through commits.
>>>>>>
>>>>>> The problem with C) and D) is that they’re hard to gather. But we could do
>>>>>> it on an ad-hoc basis by adding them to the RN during the development (when
>>>>>> they help) instead of doing it at the end.
>>>>>>
>>>>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
>>>>>> them to the Release Plan since they’re easy to find out.
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> Thanks
>>>>>> -Vincent
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thomas Mortagne
>>>
>>
>>
>>
>> --
>> Thomas Mortagne
>
>
>
> --
> Thomas Mortagne



--
Thomas Mortagne
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

Ecaterina Moraru (Valica)
+1

Hope it won't slow down the release process too much, especially since we
release now more often. Should we do this only for final versions?

Thanks,
Caty

On Mon, Feb 6, 2017 at 8:46 PM, Thomas Mortagne <[hidden email]>
wrote:

> (This is all modifications made to documents containing a translation
> object)
>
>
> On Mon, Feb 6, 2017 at 8:45 PM, Thomas Mortagne
> <[hidden email]> wrote:
> > There is a typo in the previous URL:
> > http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?
> lowerBound=20161201&upperBound=20170106
> >
> > I'm surprised $datetool.toDate does not complain about a weird date
> > like "201601201".
> >
> > On Mon, Feb 6, 2017 at 8:35 PM, Thomas Mortagne
> > <[hidden email]> wrote:
> >> Already exist: http://l10n.xwiki.org/xwiki/bin/view/L10NCode/
> BestContributorsSheet?lowerBound=201601201&upperBound=20170106
> >>
> >> What is missing is find out the dates to pass as parameters.
> >>
> >> On Mon, Feb 6, 2017 at 5:33 PM, Vincent Massol <[hidden email]>
> wrote:
> >>>
> >>>> On 6 Feb 2017, at 10:39, Thomas Mortagne <[hidden email]>
> wrote:
> >>>>
> >>>> +1 for adding any source of contributions as long as it's automated or
> >>>> close to automated (like executing one command/request and
> >>>> copy/pasting the result)
> >>>
> >>> @Thomas: Could I let you write some script to generate:
> >>> "B) The people who’ve contributed translations done after the start of
> the release development.”
> >>>
> >>> ?
> >>>
> >>> :)
> >>>
> >>> So the idea is to give a start and end date and get the list of
> translators during that period.
> >>>
> >>> Thanks
> >>> -Vincent
> >>>
> >>>> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
> >>>> <[hidden email]> wrote:
> >>>>> +1
> >>>>>
> >>>>> Thanks,
> >>>>> Marius
> >>>>>
> >>>>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]>
> wrote:
> >>>>>
> >>>>>> Hi devs,
> >>>>>>
> >>>>>> Right now we’ve started acknowledging the committers in the Release
> notes.
> >>>>>>
> >>>>>> I’d like to propose to extend that try to ack everyone who
> participates in
> >>>>>> one way or another to a release, and not just developers.
> >>>>>>
> >>>>>> I can think of 3 more items to add:
> >>>>>>
> >>>>>> A) All the JIRA issue reporters that have had an issue fixed for the
> >>>>>> release (bug, improvement, new feature, etc). They took the time to
> report
> >>>>>> an issue and thus they’ve helped the committers to improve the
> quality of
> >>>>>> the release and thus they should be acknowledged. This allows us to
> also
> >>>>>> ack QA. We could decide to exclude the reporters who’ve also been
> >>>>>> committers or leave them in.
> >>>>>>
> >>>>>> B) The people who’ve contributed translations done after the start
> of the
> >>>>>> release development.
> >>>>>>
> >>>>>> Ideally we would also ack:
> >>>>>>
> >>>>>> C) The people who’ve helped on the list for the release
> >>>>>> D) The people who’ve helped on the Design and made proposals that
> made it
> >>>>>> to the release. I’m thinking of Caty for example. Luckily Caty also
> commits
> >>>>>> some code and often she’s recognised through commits.
> >>>>>>
> >>>>>> The problem with C) and D) is that they’re hard to gather. But we
> could do
> >>>>>> it on an ad-hoc basis by adding them to the RN during the
> development (when
> >>>>>> they help) instead of doing it at the end.
> >>>>>>
> >>>>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to
> add
> >>>>>> them to the Release Plan since they’re easy to find out.
> >>>>>>
> >>>>>> WDYT?
> >>>>>>
> >>>>>> Thanks
> >>>>>> -Vincent
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Thomas Mortagne
> >>>
> >>
> >>
> >>
> >> --
> >> Thomas Mortagne
> >
> >
> >
> > --
> > Thomas Mortagne
>
>
>
> --
> Thomas Mortagne
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend the ack section of the Release Notes

vmassol
Administrator
Yes, I’d do that only for final releases (but including the participations for the RC ofc).

Thanks
-Vincent

> On 9 Feb 2017, at 13:24, Ecaterina Moraru (Valica) <[hidden email]> wrote:
>
> +1
>
> Hope it won't slow down the release process too much, especially since we
> release now more often. Should we do this only for final versions?
>
> Thanks,
> Caty
>
> On Mon, Feb 6, 2017 at 8:46 PM, Thomas Mortagne <[hidden email]>
> wrote:
>
>> (This is all modifications made to documents containing a translation
>> object)
>>
>>
>> On Mon, Feb 6, 2017 at 8:45 PM, Thomas Mortagne
>> <[hidden email]> wrote:
>>> There is a typo in the previous URL:
>>> http://l10n.xwiki.org/xwiki/bin/view/L10NCode/BestContributorsSheet?
>> lowerBound=20161201&upperBound=20170106
>>>
>>> I'm surprised $datetool.toDate does not complain about a weird date
>>> like "201601201".
>>>
>>> On Mon, Feb 6, 2017 at 8:35 PM, Thomas Mortagne
>>> <[hidden email]> wrote:
>>>> Already exist: http://l10n.xwiki.org/xwiki/bin/view/L10NCode/
>> BestContributorsSheet?lowerBound=201601201&upperBound=20170106
>>>>
>>>> What is missing is find out the dates to pass as parameters.
>>>>
>>>> On Mon, Feb 6, 2017 at 5:33 PM, Vincent Massol <[hidden email]>
>> wrote:
>>>>>
>>>>>> On 6 Feb 2017, at 10:39, Thomas Mortagne <[hidden email]>
>> wrote:
>>>>>>
>>>>>> +1 for adding any source of contributions as long as it's automated or
>>>>>> close to automated (like executing one command/request and
>>>>>> copy/pasting the result)
>>>>>
>>>>> @Thomas: Could I let you write some script to generate:
>>>>> "B) The people who’ve contributed translations done after the start of
>> the release development.”
>>>>>
>>>>> ?
>>>>>
>>>>> :)
>>>>>
>>>>> So the idea is to give a start and end date and get the list of
>> translators during that period.
>>>>>
>>>>> Thanks
>>>>> -Vincent
>>>>>
>>>>>> On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
>>>>>> <[hidden email]> wrote:
>>>>>>> +1
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Marius
>>>>>>>
>>>>>>> On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <[hidden email]>
>> wrote:
>>>>>>>
>>>>>>>> Hi devs,
>>>>>>>>
>>>>>>>> Right now we’ve started acknowledging the committers in the Release
>> notes.
>>>>>>>>
>>>>>>>> I’d like to propose to extend that try to ack everyone who
>> participates in
>>>>>>>> one way or another to a release, and not just developers.
>>>>>>>>
>>>>>>>> I can think of 3 more items to add:
>>>>>>>>
>>>>>>>> A) All the JIRA issue reporters that have had an issue fixed for the
>>>>>>>> release (bug, improvement, new feature, etc). They took the time to
>> report
>>>>>>>> an issue and thus they’ve helped the committers to improve the
>> quality of
>>>>>>>> the release and thus they should be acknowledged. This allows us to
>> also
>>>>>>>> ack QA. We could decide to exclude the reporters who’ve also been
>>>>>>>> committers or leave them in.
>>>>>>>>
>>>>>>>> B) The people who’ve contributed translations done after the start
>> of the
>>>>>>>> release development.
>>>>>>>>
>>>>>>>> Ideally we would also ack:
>>>>>>>>
>>>>>>>> C) The people who’ve helped on the list for the release
>>>>>>>> D) The people who’ve helped on the Design and made proposals that
>> made it
>>>>>>>> to the release. I’m thinking of Caty for example. Luckily Caty also
>> commits
>>>>>>>> some code and often she’s recognised through commits.
>>>>>>>>
>>>>>>>> The problem with C) and D) is that they’re hard to gather. But we
>> could do
>>>>>>>> it on an ad-hoc basis by adding them to the RN during the
>> development (when
>>>>>>>> they help) instead of doing it at the end.
>>>>>>>>
>>>>>>>> In any case I’d like to focus on A) and B) FTM and I’m proposing to
>> add
>>>>>>>> them to the Release Plan since they’re easy to find out.
>>>>>>>>
>>>>>>>> WDYT?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> -Vincent
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thomas Mortagne
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thomas Mortagne
>>>
>>>
>>>
>>> --
>>> Thomas Mortagne
>>
>>
>>
>> --
>> Thomas Mortagne
>>