Re: Is Open Office Going Away?

2019-09-21 Thread Marcus

Am 18.09.19 um 17:16 schrieb Mike Kuldayev:
I'm working in an online school and our teachers frequently encourage 
their students to download Open Office for free from your homepage. 
Recently, I've got wind that Open Office might be going away and/or 
students won't be able to download it for free in the near future. So, I 
just wanted to follow up with you to see if that's truly the case or 
just empty rumor?


you have a great timing.

Today we have published a new release[1][2].

And this is the best proof that the project cannot be not dead. Isn't 
it? ;-)


Apache OpenOffice was, is and will be available for free for everyone.

[1] http://www.openoffice.org/download/
[2] https://blogs.apache.org/OOo/entry/announcing-apache-openoffice-4-13

Marcus


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



Re: Is Open Office Going Away?

2019-09-21 Thread Jose R R
On Sat, Sep 21, 2019 at 5:08 AM Mike Kuldayev <
academ...@enlightiumacademy.com> wrote:

> Hello,
>
> I'm working in an online school and our teachers frequently encourage
> their students to download Open Office for free from your homepage.
> Recently, I've got wind that Open Office might be going away
>
Not, as far as I am concerned. Voting on next 4.1.7 version release just
completed ;-)



> and/or students won't be able to download it for free in the near future.
>
Also, absolutely false. As a matter of fact AOO seems going on so strong
that commercial (i.e., Microsoft) and open source alternatives (i.e.,
LibreOffice) are suspected of disseminating fear, uncertainty, and doubt
(FUD) against Apache Open Office (AOO).



> So, I just wanted to follow up with you to see if that's truly the case or
> just empty rumor?
>
> Thank you much,
>
> MK
>
> *Mike Kuldayev*
>
> History Department Head & AP/CC Teacher
>
> *___*
>
> *P:* 509-319-2402 *F:* 888-317-6571
>
>
> academ...@enlightiumacademy.com
>
> www.enlightiumacademy.com
>
> 
> The information contained in this message is privileged and confidential.
> It is intended solely for the use of the named recipient. If you are not
> the intended recipient, you are hereby notified that any disclosure,
> copying, distribution, or use of the contents of this transmission is
> strictly prohibited. If you receive this message in error, please notify
> the sender immediately. Thank you.
>
> 
> *Enlightium Academy Disclaimer*
>

Best Professional Regards.
-- 
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Stretch w/ Linux 5.2.10 AMD64
-
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
---
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/


Is Open Office Going Away?

2019-09-21 Thread Mike Kuldayev
Hello,

I'm working in an online school and our teachers frequently encourage their
students to download Open Office for free from your homepage. Recently,
I've got wind that Open Office might be going away and/or students won't be
able to download it for free in the near future. So, I just wanted to
follow up with you to see if that's truly the case or just empty rumor?

Thank you much,

MK





Re: Google+ going away on April 2, 2019

2019-03-21 Thread Kay Schenk
+1 to this Matthias. Ok, the archive I just created seems to be in a LOT 
more usable form than the earlier one I did a few weeks ago. I will try 
to just generate a LARGE html file to put somewhere.


"Less is more."

MzK


On 3/21/19 9:24 AM, Matthias Seidel wrote:

Hi Kay,

Am 19.03.19 um 01:48 schrieb Kay Schenk:

Hi. Is MeWe a social platform we want to explore? I'm assuming we'd need to
have an account. I'm fairly certain I can figure out how to "show" the AOO
posts on a Web site but that would be the end of the line.

It would just be another platform...

I'd rather see that Facebook and Twitter are properly maintained.

Regards,

    Matthias


I have NOT investigated how to upload them to the Forum. That's already a
conversational vehicle.
Hoping to get back to all this this week.



___
Sent from MzK's phone.

On Thu, Mar 14, 2019, 17:18 Matthias Seidel 
wrote:


Hi Kay,


Am 26.02.19 um 22:25 schrieb Kay Schenk:

On 2/24/19 12:59 PM, Matthias Seidel wrote:

Hi Kay, Hi Keith,

Am 05.02.19 um 00:58 schrieb Kay Schenk:

On 2/2/19 11:07 AM, Keith N. McKenna wrote:

On 2/2/2019 1:00 PM, Kay Schenk wrote:

I'm assuming most of you know that Google+ is going away April 2.
2019.
I am one of the moderators for the AOO group. Here is information I
just
received. I know MANY are disappointed by this decision, and we
need to
discuss what to do with the current AOO information.

I just found this:


https://techaeris.com/2019/02/15/the-mewe-social-network-made-a-tool-to-import-your-google-data-to-their-platform/

Regards

Matthias


Hi Kay;

Yes we should definitely make an archive of Google+ pages, just not
sure
where the best place for them to be stored would be.

Regards
Keith


I'm looking into HOW to get the data from G+. It might be nice
(somehow) to import the G+ postings into FB, but the participant info
wouldn't sync that's for sure. I'll do a dump from G+ soon and see
what the feeds/post look like.

You may already have found the way to archive Google+ content:
https://takeout.google.com/

It took Google about one week to provide my zip file.

I am also wondering about our YouTube channel. It is linked to the
Google+ brand account, so I have administrative rights. But since I am
not the owner I can not add another administrator/moderator.

Regards,

 Matthias

A short update. I just "downloaded" the set from Apache OpenOffice G+.
It didn't take very long. I actually used the instructions from:

https://support.google.com/plus/answer/1045788

All the posts are there but...the urls generated reference
"plus.google.com" which is useless since that's the service going
away. So, I will look around to see what else I can find. Oy! Maybe we
can find the G+ stylesheets somewhere.


"Less is more."

MzK



--
MzK



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




Re: Google+ going away on April 2, 2019

2019-03-21 Thread Matthias Seidel
Hi Kay,

Am 19.03.19 um 01:48 schrieb Kay Schenk:
> Hi. Is MeWe a social platform we want to explore? I'm assuming we'd need to
> have an account. I'm fairly certain I can figure out how to "show" the AOO
> posts on a Web site but that would be the end of the line.

It would just be another platform...

I'd rather see that Facebook and Twitter are properly maintained.

Regards,

   Matthias

> I have NOT investigated how to upload them to the Forum. That's already a
> conversational vehicle.
> Hoping to get back to all this this week.
>
>
>
> ___
> Sent from MzK's phone.
>
> On Thu, Mar 14, 2019, 17:18 Matthias Seidel 
> wrote:
>
>> Hi Kay,
>>
>>
>> Am 26.02.19 um 22:25 schrieb Kay Schenk:
>>> On 2/24/19 12:59 PM, Matthias Seidel wrote:
>>>> Hi Kay, Hi Keith,
>>>>
>>>> Am 05.02.19 um 00:58 schrieb Kay Schenk:
>>>>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>>>>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>>>>>> I'm assuming most of you know that Google+ is going away April 2.
>>>>>>> 2019.
>>>>>>> I am one of the moderators for the AOO group. Here is information I
>>>>>>> just
>>>>>>> received. I know MANY are disappointed by this decision, and we
>>>>>>> need to
>>>>>>> discuss what to do with the current AOO information.
>> I just found this:
>>
>>
>> https://techaeris.com/2019/02/15/the-mewe-social-network-made-a-tool-to-import-your-google-data-to-their-platform/
>>
>> Regards
>>
>>Matthias
>>
>>>>>> Hi Kay;
>>>>>>
>>>>>> Yes we should definitely make an archive of Google+ pages, just not
>>>>>> sure
>>>>>> where the best place for them to be stored would be.
>>>>>>
>>>>>> Regards
>>>>>> Keith
>>>>>>
>>>>> I'm looking into HOW to get the data from G+. It might be nice
>>>>> (somehow) to import the G+ postings into FB, but the participant info
>>>>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
>>>>> what the feeds/post look like.
>>>> You may already have found the way to archive Google+ content:
>>>> https://takeout.google.com/
>>>>
>>>> It took Google about one week to provide my zip file.
>>>>
>>>> I am also wondering about our YouTube channel. It is linked to the
>>>> Google+ brand account, so I have administrative rights. But since I am
>>>> not the owner I can not add another administrator/moderator.
>>>>
>>>> Regards,
>>>>
>>>> Matthias
>>> A short update. I just "downloaded" the set from Apache OpenOffice G+.
>>> It didn't take very long. I actually used the instructions from:
>>>
>>> https://support.google.com/plus/answer/1045788
>>>
>>> All the posts are there but...the urls generated reference
>>> "plus.google.com" which is useless since that's the service going
>>> away. So, I will look around to see what else I can find. Oy! Maybe we
>>> can find the G+ stylesheets somewhere.
>>>
>>>
>>> "Less is more."
>>> 
>>> MzK
>>>
>>>
>>>>> --
>>>>> MzK
>>>>>
>>>>>
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>
>>>>>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Google+ going away on April 2, 2019

2019-03-18 Thread Kay Schenk
Hi. Is MeWe a social platform we want to explore? I'm assuming we'd need to
have an account. I'm fairly certain I can figure out how to "show" the AOO
posts on a Web site but that would be the end of the line.

I have NOT investigated how to upload them to the Forum. That's already a
conversational vehicle.
Hoping to get back to all this this week.



___
Sent from MzK's phone.

On Thu, Mar 14, 2019, 17:18 Matthias Seidel 
wrote:

> Hi Kay,
>
>
> Am 26.02.19 um 22:25 schrieb Kay Schenk:
> >
> > On 2/24/19 12:59 PM, Matthias Seidel wrote:
> >> Hi Kay, Hi Keith,
> >>
> >> Am 05.02.19 um 00:58 schrieb Kay Schenk:
> >>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
> >>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
> >>>>> I'm assuming most of you know that Google+ is going away April 2.
> >>>>> 2019.
> >>>>> I am one of the moderators for the AOO group. Here is information I
> >>>>> just
> >>>>> received. I know MANY are disappointed by this decision, and we
> >>>>> need to
> >>>>> discuss what to do with the current AOO information.
>
> I just found this:
>
>
> https://techaeris.com/2019/02/15/the-mewe-social-network-made-a-tool-to-import-your-google-data-to-their-platform/
>
> Regards
>
>Matthias
>
> >>>>>
> >>>> Hi Kay;
> >>>>
> >>>> Yes we should definitely make an archive of Google+ pages, just not
> >>>> sure
> >>>> where the best place for them to be stored would be.
> >>>>
> >>>> Regards
> >>>> Keith
> >>>>
> >>> I'm looking into HOW to get the data from G+. It might be nice
> >>> (somehow) to import the G+ postings into FB, but the participant info
> >>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
> >>> what the feeds/post look like.
> >> You may already have found the way to archive Google+ content:
> >> https://takeout.google.com/
> >>
> >> It took Google about one week to provide my zip file.
> >>
> >> I am also wondering about our YouTube channel. It is linked to the
> >> Google+ brand account, so I have administrative rights. But since I am
> >> not the owner I can not add another administrator/moderator.
> >>
> >> Regards,
> >>
> >> Matthias
> >
> > A short update. I just "downloaded" the set from Apache OpenOffice G+.
> > It didn't take very long. I actually used the instructions from:
> >
> > https://support.google.com/plus/answer/1045788
> >
> > All the posts are there but...the urls generated reference
> > "plus.google.com" which is useless since that's the service going
> > away. So, I will look around to see what else I can find. Oy! Maybe we
> > can find the G+ stylesheets somewhere.
> >
> >
> > "Less is more."
> > 
> > MzK
> >
> >
> >>
> >>> --
> >>> MzK
> >>>
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>>
> >>>
> >
>
>


Re: Google+ going away on April 2, 2019

2019-03-14 Thread Matthias Seidel
Hi Kay,


Am 26.02.19 um 22:25 schrieb Kay Schenk:
>
> On 2/24/19 12:59 PM, Matthias Seidel wrote:
>> Hi Kay, Hi Keith,
>>
>> Am 05.02.19 um 00:58 schrieb Kay Schenk:
>>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>>>> I'm assuming most of you know that Google+ is going away April 2.
>>>>> 2019.
>>>>> I am one of the moderators for the AOO group. Here is information I
>>>>> just
>>>>> received. I know MANY are disappointed by this decision, and we
>>>>> need to
>>>>> discuss what to do with the current AOO information.

I just found this:

https://techaeris.com/2019/02/15/the-mewe-social-network-made-a-tool-to-import-your-google-data-to-their-platform/

Regards

   Matthias

>>>>>
>>>> Hi Kay;
>>>>
>>>> Yes we should definitely make an archive of Google+ pages, just not
>>>> sure
>>>> where the best place for them to be stored would be.
>>>>
>>>> Regards
>>>> Keith
>>>>
>>> I'm looking into HOW to get the data from G+. It might be nice
>>> (somehow) to import the G+ postings into FB, but the participant info
>>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
>>> what the feeds/post look like.
>> You may already have found the way to archive Google+ content:
>> https://takeout.google.com/
>>
>> It took Google about one week to provide my zip file.
>>
>> I am also wondering about our YouTube channel. It is linked to the
>> Google+ brand account, so I have administrative rights. But since I am
>> not the owner I can not add another administrator/moderator.
>>
>> Regards,
>>
>>     Matthias
>
> A short update. I just "downloaded" the set from Apache OpenOffice G+.
> It didn't take very long. I actually used the instructions from:
>
> https://support.google.com/plus/answer/1045788
>
> All the posts are there but...the urls generated reference
> "plus.google.com" which is useless since that's the service going
> away. So, I will look around to see what else I can find. Oy! Maybe we
> can find the G+ stylesheets somewhere.
>
>
> "Less is more."
> 
> MzK
>
>
>>
>>> --
>>> MzK
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Google+ going away on April 2, 2019

2019-02-28 Thread Peter Kovacs
+1 from my side. I think this is awesome development!

On 28.02.19 10:59, Matthias Seidel wrote:
> Hi all,
>
> Am 26.02.19 um 06:45 schrieb Peter Kovacs:
>> Does it make sense to contact google to try to regain control over the
>> account?
> I am happy to say, that I got the primary ownership for our Apache
> OpenOffice brand account from Ariel.
> With Google+ going away, we should now get some content in our YouTube
> channel (271 subscriber).
>
> @Kay: I would like to add you as administrator...
>
> Regards,
>
>    Matthias
>
>> On 25.02.19 01:27, Kay Schenk wrote:
>>> On Sun, Feb 24, 2019, 15:41 Matthias Seidel 
>>> wrote:
>>>
>>>> Hi Kay,
>>>>
>>>> Am 25.02.19 um 00:24 schrieb Kay Schenk:
>>>>> On 2/24/19 12:59 PM, Matthias Seidel wrote:
>>>>>> Hi Kay, Hi Keith,
>>>>>>
>>>>>> Am 05.02.19 um 00:58 schrieb Kay Schenk:
>>>>>>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>>>>>>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>>>>>>>> I'm assuming most of you know that Google+ is going away April 2.
>>>>>>>>> 2019.
>>>>>>>>> I am one of the moderators for the AOO group. Here is information I
>>>>>>>>> just
>>>>>>>>> received. I know MANY are disappointed by this decision, and we
>>>>>>>>> need to
>>>>>>>>> discuss what to do with the current AOO information.
>>>>>>>>>
>>>>>>>> Hi Kay;
>>>>>>>>
>>>>>>>> Yes we should definitely make an archive of Google+ pages, just not
>>>>>>>> sure
>>>>>>>> where the best place for them to be stored would be.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Keith
>>>>>>>>
>>>>>>> I'm looking into HOW to get the data from G+. It might be nice
>>>>>>> (somehow) to import the G+ postings into FB, but the participant info
>>>>>>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
>>>>>>> what the feeds/post look like.
>>>>> OK. That would be great. I don't do much programming of late. We MAY
>>>>> be able to use one of their APIs (not investigated yet!) to do SOMETHING.
>>>>>> You may already have found the way to archive Google+ content:
>>>>>> https://takeout.google.com/
>>>>> Yes, I have seen this. I've done nothing yet. I should get to doing an
>>>>> archive this week sometime.
>>>>>
>>>>>
>>>>>> It took Google about one week to provide my zip file.
>>>>> GEE WHIZ! That's kind of unbelievable.
>>>>>
>>>>>
>>>>>> I am also wondering about our YouTube channel. It is linked to the
>>>>>> Google+ brand account, so I have administrative rights. But since I am
>>>>>> not the owner I can not add another administrator/moderator.
>>>>> YouTube is NOT being affected as far as I know.
>>>> YouTube itself is not affected. But the right management is linked with
>>>> Googles brand accounts.
>>>> And "our" brand account is owned by Ariel Constenla-Haile.
>>>>
>>>> So I will still be able to administrate our Channel but I can't do
>>>> anything beyond that.
>>>> And I will be the only one who has access.
>>>>
>>>> Regards,
>>>>
>>>>Matthias
>>>>
>>> Got it.
>>>
>>>
>>>>>> Regards,
>>>>>>
>>>>>> Matthias
>>>>> Thanks for looking into this.
>>>>>>> --
>>>>>>> MzK
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

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



Re: Google+ going away on April 2, 2019

2019-02-28 Thread Matthias Seidel
Hi all,

Am 26.02.19 um 06:45 schrieb Peter Kovacs:
> Does it make sense to contact google to try to regain control over the
> account?

I am happy to say, that I got the primary ownership for our Apache
OpenOffice brand account from Ariel.
With Google+ going away, we should now get some content in our YouTube
channel (271 subscriber).

@Kay: I would like to add you as administrator...

Regards,

   Matthias

>
> On 25.02.19 01:27, Kay Schenk wrote:
>> On Sun, Feb 24, 2019, 15:41 Matthias Seidel 
>> wrote:
>>
>>> Hi Kay,
>>>
>>> Am 25.02.19 um 00:24 schrieb Kay Schenk:
>>>> On 2/24/19 12:59 PM, Matthias Seidel wrote:
>>>>> Hi Kay, Hi Keith,
>>>>>
>>>>> Am 05.02.19 um 00:58 schrieb Kay Schenk:
>>>>>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>>>>>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>>>>>>> I'm assuming most of you know that Google+ is going away April 2.
>>>>>>>> 2019.
>>>>>>>> I am one of the moderators for the AOO group. Here is information I
>>>>>>>> just
>>>>>>>> received. I know MANY are disappointed by this decision, and we
>>>>>>>> need to
>>>>>>>> discuss what to do with the current AOO information.
>>>>>>>>
>>>>>>> Hi Kay;
>>>>>>>
>>>>>>> Yes we should definitely make an archive of Google+ pages, just not
>>>>>>> sure
>>>>>>> where the best place for them to be stored would be.
>>>>>>>
>>>>>>> Regards
>>>>>>> Keith
>>>>>>>
>>>>>> I'm looking into HOW to get the data from G+. It might be nice
>>>>>> (somehow) to import the G+ postings into FB, but the participant info
>>>>>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
>>>>>> what the feeds/post look like.
>>>> OK. That would be great. I don't do much programming of late. We MAY
>>>> be able to use one of their APIs (not investigated yet!) to do SOMETHING.
>>>>> You may already have found the way to archive Google+ content:
>>>>> https://takeout.google.com/
>>>> Yes, I have seen this. I've done nothing yet. I should get to doing an
>>>> archive this week sometime.
>>>>
>>>>
>>>>> It took Google about one week to provide my zip file.
>>>> GEE WHIZ! That's kind of unbelievable.
>>>>
>>>>
>>>>> I am also wondering about our YouTube channel. It is linked to the
>>>>> Google+ brand account, so I have administrative rights. But since I am
>>>>> not the owner I can not add another administrator/moderator.
>>>> YouTube is NOT being affected as far as I know.
>>> YouTube itself is not affected. But the right management is linked with
>>> Googles brand accounts.
>>> And "our" brand account is owned by Ariel Constenla-Haile.
>>>
>>> So I will still be able to administrate our Channel but I can't do
>>> anything beyond that.
>>> And I will be the only one who has access.
>>>
>>> Regards,
>>>
>>>Matthias
>>>
>> Got it.
>>
>>
>>>>> Regards,
>>>>>
>>>>> Matthias
>>>> Thanks for looking into this.
>>>>>> --
>>>>>> MzK
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Google+ going away on April 2, 2019

2019-02-26 Thread Kay Schenk



On 2/24/19 12:59 PM, Matthias Seidel wrote:

Hi Kay, Hi Keith,

Am 05.02.19 um 00:58 schrieb Kay Schenk:

On 2/2/19 11:07 AM, Keith N. McKenna wrote:

On 2/2/2019 1:00 PM, Kay Schenk wrote:

I'm assuming most of you know that Google+ is going away April 2. 2019.
I am one of the moderators for the AOO group. Here is information I
just
received. I know MANY are disappointed by this decision, and we need to
discuss what to do with the current AOO information.


Hi Kay;

Yes we should definitely make an archive of Google+ pages, just not sure
where the best place for them to be stored would be.

Regards
Keith


I'm looking into HOW to get the data from G+. It might be nice
(somehow) to import the G+ postings into FB, but the participant info
wouldn't sync that's for sure. I'll do a dump from G+ soon and see
what the feeds/post look like.

You may already have found the way to archive Google+ content:
https://takeout.google.com/

It took Google about one week to provide my zip file.

I am also wondering about our YouTube channel. It is linked to the
Google+ brand account, so I have administrative rights. But since I am
not the owner I can not add another administrator/moderator.

Regards,

    Matthias


A short update. I just "downloaded" the set from Apache OpenOffice G+. 
It didn't take very long. I actually used the instructions from:


https://support.google.com/plus/answer/1045788

All the posts are there but...the urls generated reference 
"plus.google.com" which is useless since that's the service going away. 
So, I will look around to see what else I can find. Oy! Maybe we can 
find the G+ stylesheets somewhere.



"Less is more."

MzK





--
MzK



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




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



Re: Google+ going away on April 2, 2019

2019-02-25 Thread Peter Kovacs
Does it make sense to contact google to try to regain control over the
account?


On 25.02.19 01:27, Kay Schenk wrote:
> On Sun, Feb 24, 2019, 15:41 Matthias Seidel 
> wrote:
>
>> Hi Kay,
>>
>> Am 25.02.19 um 00:24 schrieb Kay Schenk:
>>> On 2/24/19 12:59 PM, Matthias Seidel wrote:
>>>> Hi Kay, Hi Keith,
>>>>
>>>> Am 05.02.19 um 00:58 schrieb Kay Schenk:
>>>>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>>>>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>>>>>> I'm assuming most of you know that Google+ is going away April 2.
>>>>>>> 2019.
>>>>>>> I am one of the moderators for the AOO group. Here is information I
>>>>>>> just
>>>>>>> received. I know MANY are disappointed by this decision, and we
>>>>>>> need to
>>>>>>> discuss what to do with the current AOO information.
>>>>>>>
>>>>>> Hi Kay;
>>>>>>
>>>>>> Yes we should definitely make an archive of Google+ pages, just not
>>>>>> sure
>>>>>> where the best place for them to be stored would be.
>>>>>>
>>>>>> Regards
>>>>>> Keith
>>>>>>
>>>>> I'm looking into HOW to get the data from G+. It might be nice
>>>>> (somehow) to import the G+ postings into FB, but the participant info
>>>>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
>>>>> what the feeds/post look like.
>>> OK. That would be great. I don't do much programming of late. We MAY
>>> be able to use one of their APIs (not investigated yet!) to do SOMETHING.
>>>> You may already have found the way to archive Google+ content:
>>>> https://takeout.google.com/
>>> Yes, I have seen this. I've done nothing yet. I should get to doing an
>>> archive this week sometime.
>>>
>>>
>>>> It took Google about one week to provide my zip file.
>>> GEE WHIZ! That's kind of unbelievable.
>>>
>>>
>>>> I am also wondering about our YouTube channel. It is linked to the
>>>> Google+ brand account, so I have administrative rights. But since I am
>>>> not the owner I can not add another administrator/moderator.
>>> YouTube is NOT being affected as far as I know.
>> YouTube itself is not affected. But the right management is linked with
>> Googles brand accounts.
>> And "our" brand account is owned by Ariel Constenla-Haile.
>>
>> So I will still be able to administrate our Channel but I can't do
>> anything beyond that.
>> And I will be the only one who has access.
>>
>> Regards,
>>
>>Matthias
>>
> Got it.
>
>
>>>> Regards,
>>>>
>>>> Matthias
>>> Thanks for looking into this.
>>>>> --
>>>>> MzK
>>>>>
>>>>>
>>>>>
>>>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>

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



Re: Google+ going away on April 2, 2019

2019-02-24 Thread Kay Schenk
On Sun, Feb 24, 2019, 15:41 Matthias Seidel 
wrote:

> Hi Kay,
>
> Am 25.02.19 um 00:24 schrieb Kay Schenk:
> >
> > On 2/24/19 12:59 PM, Matthias Seidel wrote:
> >> Hi Kay, Hi Keith,
> >>
> >> Am 05.02.19 um 00:58 schrieb Kay Schenk:
> >>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
> >>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
> >>>>> I'm assuming most of you know that Google+ is going away April 2.
> >>>>> 2019.
> >>>>> I am one of the moderators for the AOO group. Here is information I
> >>>>> just
> >>>>> received. I know MANY are disappointed by this decision, and we
> >>>>> need to
> >>>>> discuss what to do with the current AOO information.
> >>>>>
> >>>> Hi Kay;
> >>>>
> >>>> Yes we should definitely make an archive of Google+ pages, just not
> >>>> sure
> >>>> where the best place for them to be stored would be.
> >>>>
> >>>> Regards
> >>>> Keith
> >>>>
> >>> I'm looking into HOW to get the data from G+. It might be nice
> >>> (somehow) to import the G+ postings into FB, but the participant info
> >>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
> >>> what the feeds/post look like.
> > OK. That would be great. I don't do much programming of late. We MAY
> > be able to use one of their APIs (not investigated yet!) to do SOMETHING.
> >> You may already have found the way to archive Google+ content:
> >> https://takeout.google.com/
> >
> > Yes, I have seen this. I've done nothing yet. I should get to doing an
> > archive this week sometime.
> >
> >
> >>
> >> It took Google about one week to provide my zip file.
> >
> > GEE WHIZ! That's kind of unbelievable.
> >
> >
> >>
> >> I am also wondering about our YouTube channel. It is linked to the
> >> Google+ brand account, so I have administrative rights. But since I am
> >> not the owner I can not add another administrator/moderator.
> >
> > YouTube is NOT being affected as far as I know.
>
> YouTube itself is not affected. But the right management is linked with
> Googles brand accounts.
> And "our" brand account is owned by Ariel Constenla-Haile.
>
> So I will still be able to administrate our Channel but I can't do
> anything beyond that.
> And I will be the only one who has access.
>
> Regards,
>
>Matthias
>

Got it.


> >
> >>
> >> Regards,
> >>
> >> Matthias
> > Thanks for looking into this.
> >>
> >>> --
> >>> MzK
> >>>
> >>>
> >>>
> >>>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>


Re: Google+ going away on April 2, 2019

2019-02-24 Thread Matthias Seidel
Hi Kay,

Am 25.02.19 um 00:24 schrieb Kay Schenk:
>
> On 2/24/19 12:59 PM, Matthias Seidel wrote:
>> Hi Kay, Hi Keith,
>>
>> Am 05.02.19 um 00:58 schrieb Kay Schenk:
>>> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>>>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>>>> I'm assuming most of you know that Google+ is going away April 2.
>>>>> 2019.
>>>>> I am one of the moderators for the AOO group. Here is information I
>>>>> just
>>>>> received. I know MANY are disappointed by this decision, and we
>>>>> need to
>>>>> discuss what to do with the current AOO information.
>>>>>
>>>> Hi Kay;
>>>>
>>>> Yes we should definitely make an archive of Google+ pages, just not
>>>> sure
>>>> where the best place for them to be stored would be.
>>>>
>>>> Regards
>>>> Keith
>>>>
>>> I'm looking into HOW to get the data from G+. It might be nice
>>> (somehow) to import the G+ postings into FB, but the participant info
>>> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
>>> what the feeds/post look like.
> OK. That would be great. I don't do much programming of late. We MAY
> be able to use one of their APIs (not investigated yet!) to do SOMETHING.
>> You may already have found the way to archive Google+ content:
>> https://takeout.google.com/
>
> Yes, I have seen this. I've done nothing yet. I should get to doing an
> archive this week sometime.
>
>
>>
>> It took Google about one week to provide my zip file.
>
> GEE WHIZ! That's kind of unbelievable.
>
>
>>
>> I am also wondering about our YouTube channel. It is linked to the
>> Google+ brand account, so I have administrative rights. But since I am
>> not the owner I can not add another administrator/moderator.
>
> YouTube is NOT being affected as far as I know.

YouTube itself is not affected. But the right management is linked with
Googles brand accounts.
And "our" brand account is owned by Ariel Constenla-Haile.

So I will still be able to administrate our Channel but I can't do
anything beyond that.
And I will be the only one who has access.

Regards,

   Matthias

>
>>
>> Regards,
>>
>>     Matthias
> Thanks for looking into this.
>>
>>> --
>>> MzK
>>>
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Google+ going away on April 2, 2019

2019-02-24 Thread Kay Schenk



On 2/24/19 12:59 PM, Matthias Seidel wrote:

Hi Kay, Hi Keith,

Am 05.02.19 um 00:58 schrieb Kay Schenk:

On 2/2/19 11:07 AM, Keith N. McKenna wrote:

On 2/2/2019 1:00 PM, Kay Schenk wrote:

I'm assuming most of you know that Google+ is going away April 2. 2019.
I am one of the moderators for the AOO group. Here is information I
just
received. I know MANY are disappointed by this decision, and we need to
discuss what to do with the current AOO information.


Hi Kay;

Yes we should definitely make an archive of Google+ pages, just not sure
where the best place for them to be stored would be.

Regards
Keith


I'm looking into HOW to get the data from G+. It might be nice
(somehow) to import the G+ postings into FB, but the participant info
wouldn't sync that's for sure. I'll do a dump from G+ soon and see
what the feeds/post look like.
OK. That would be great. I don't do much programming of late. We MAY be 
able to use one of their APIs (not investigated yet!) to do SOMETHING.

You may already have found the way to archive Google+ content:
https://takeout.google.com/


Yes, I have seen this. I've done nothing yet. I should get to doing an 
archive this week sometime.





It took Google about one week to provide my zip file.


GEE WHIZ! That's kind of unbelievable.




I am also wondering about our YouTube channel. It is linked to the
Google+ brand account, so I have administrative rights. But since I am
not the owner I can not add another administrator/moderator.


YouTube is NOT being affected as far as I know.



Regards,

    Matthias

Thanks for looking into this.



--
MzK






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



Re: Google+ going away on April 2, 2019

2019-02-24 Thread Matthias Seidel
Hi Kay, Hi Keith,

Am 05.02.19 um 00:58 schrieb Kay Schenk:
>
> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>> I'm assuming most of you know that Google+ is going away April 2. 2019.
>>> I am one of the moderators for the AOO group. Here is information I
>>> just
>>> received. I know MANY are disappointed by this decision, and we need to
>>> discuss what to do with the current AOO information.
>>>
>> Hi Kay;
>>
>> Yes we should definitely make an archive of Google+ pages, just not sure
>> where the best place for them to be stored would be.
>>
>> Regards
>> Keith
>>
>
> I'm looking into HOW to get the data from G+. It might be nice
> (somehow) to import the G+ postings into FB, but the participant info
> wouldn't sync that's for sure. I'll do a dump from G+ soon and see
> what the feeds/post look like.

You may already have found the way to archive Google+ content:
https://takeout.google.com/

It took Google about one week to provide my zip file.

I am also wondering about our YouTube channel. It is linked to the
Google+ brand account, so I have administrative rights. But since I am
not the owner I can not add another administrator/moderator.

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Google+ going away on April 2, 2019

2019-02-06 Thread Keith N. McKenna
On 2/4/2019 6:58 PM, Kay Schenk wrote:
> 
> On 2/2/19 11:07 AM, Keith N. McKenna wrote:
>> On 2/2/2019 1:00 PM, Kay Schenk wrote:
>>> I'm assuming most of you know that Google+ is going away April 2. 2019.
>>> I am one of the moderators for the AOO group. Here is information I just
>>> received. I know MANY are disappointed by this decision, and we need to
>>> discuss what to do with the current AOO information.
>>>
>> Hi Kay;
>>
>> Yes we should definitely make an archive of Google+ pages, just not sure
>> where the best place for them to be stored would be.
>>
>> Regards
>> Keith
>>
> 
> I'm looking into HOW to get the data from G+. It might be nice (somehow)
> to import the G+ postings into FB, but the participant info wouldn't
> sync that's for sure. I'll do a dump from G+ soon and see what the
> feeds/post look like.
> --
> MzK

Sounds good.




signature.asc
Description: OpenPGP digital signature


Re: Google+ going away on April 2, 2019

2019-02-04 Thread Kay Schenk



On 2/2/19 11:07 AM, Keith N. McKenna wrote:

On 2/2/2019 1:00 PM, Kay Schenk wrote:

I'm assuming most of you know that Google+ is going away April 2. 2019.
I am one of the moderators for the AOO group. Here is information I just
received. I know MANY are disappointed by this decision, and we need to
discuss what to do with the current AOO information.


Hi Kay;

Yes we should definitely make an archive of Google+ pages, just not sure
where the best place for them to be stored would be.

Regards
Keith



I'm looking into HOW to get the data from G+. It might be nice (somehow) 
to import the G+ postings into FB, but the participant info wouldn't 
sync that's for sure. I'll do a dump from G+ soon and see what the 
feeds/post look like.

--
MzK



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



Re: Google+ going away on April 2, 2019

2019-02-02 Thread Keith N. McKenna
On 2/2/2019 1:00 PM, Kay Schenk wrote:
> I'm assuming most of you know that Google+ is going away April 2. 2019.
> I am one of the moderators for the AOO group. Here is information I just
> received. I know MANY are disappointed by this decision, and we need to
> discuss what to do with the current AOO information.
> 
Hi Kay;

Yes we should definitely make an archive of Google+ pages, just not sure
where the best place for them to be stored would be.

Regards
Keith



signature.asc
Description: OpenPGP digital signature


Google+ going away on April 2, 2019

2019-02-02 Thread Kay Schenk
I'm assuming most of you know that Google+ is going away April 2. 2019. 
I am one of the moderators for the AOO group. Here is information I just 
received. I know MANY are disappointed by this decision, and we need to 
discuss what to do with the current AOO information.


___

*You've received this email because you have a consumer (personal) 
Google+ account or you manage a Google+ page.*


In December 2018, we announced 
<https://blog.google/technology/safety-security/expediting-changes-google-plus> 
our decision to shut down Google+ for consumers in April 2019 due to low 
usage and challenges involved in maintaining a successful product that 
meets consumers' expectations. We want to thank you for being part of 
Google+ and provide next steps, including how to download your photos 
and other content.


*On April 2nd, your Google+ account and any Google+ pages you created 
will be shut down and we will begin deleting content from consumer 
Google+ accounts*. Photos and videos from Google+ in your Album Archive 
and your Google+ pages will also be deleted. You can download and save 
<https://support.google.com/plus/answer/1045788> your content, just make 
sure to do so before April. Note that photos and videos backed up in 
Google Photos will not be deleted.


The process of deleting content from consumer Google+ accounts, Google+ 
Pages, and Album Archive will take a few months, and content may remain 
through this time. For example, users may still see parts of their 
Google+ account via activity log and some consumer Google+ content may 
remain visible to G Suite users until consumer Google+ is deleted.


*As early as February 4th, you will no longer be able to create new 
Google+ profiles, pages, communities or events.*


See the full FAQ <https://support.google.com/plus/answer/9217723> for 
more details and updates leading up to the shutdown.


*If you're a Google+ Community owner or moderator*, you may download and 
save <https://support.google.com/plus/answer/1045788> your data for your 
Google+ Community. Starting early March 2019, additional data will be 
available for download, including author, body, and photos for every 
community post in a public community. Learn more 
<https://support.google.com/plus/answer/1045788#communities>


*If you sign in to sites and apps using the Google+ Sign-in button*, 
these buttons will stop working in the coming weeks but in some cases 
may be replaced by a Google Sign-in button. You'll still be able to sign 
in with your Google Account wherever you see Google Sign-in buttons. 
Learn more <https://support.google.com/plus/answer/9217723#signin>


*If you've used Google+ for comments on your own or other sites*, this 
feature will be removed from Blogger by February 4th and other sites by 
March 7th. All your Google+ comments on all sites will be deleted 
starting April 2, 2019. Learn more 
<https://support.google.com/plus/answer/9217723#blogger>


*If you're a G Suite customer*, Google+ for your G Suite account should 
remain active. Contact your G Suite administrator 
<https://support.google.com/a/answer/6208960> for more details. You can 
also expect a new look and new features soon. Learn more 
<https://cloud.google.com/blog/products/g-suite/new-enterprise-grade-features-in-googleplus-help-businesses-drive-collaboration>


*If you're a developer* using Google+ APIs or Google+ Sign-in, click 
here <https://developers.google.com/+/api-shutdown> to see how this will 
impact you.


From all of us on the Google+ team, thank you for making Google+ such a 
special place. We are grateful for the talented group of artists, 
community builders, and thought leaders who made Google+ their home. It 
would not have been the same without your passion and dedication.


Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043

You have received this mandatory email service announcement to update 
you about important changes to your Google+ Page, product or account.


--
--
MzK




Re: [proposal] going Agile

2018-02-18 Thread Peter Kovacs
After some thinking, I think this is not easy to answer without more 
clarification.


So I have updated the List I have once started (Now called Points of 
Interest). Added the going Agile topic, and will clarify the Point.


So no one has to read this discussion in order to get the picture.


The List contains more points. That are points I think they are 
interesting to look into, my top points have my name behind them.


If anyone wants to add points or clarify points, please feel free to 
edit / extend with sub pages.


I have added my name behind the points I put currently focus on.




On 18.02.2018 00:52, Peter kovacs wrote:

How long should a reasonable demonstration period be?

And what are the success criterias that has to be fulfilled?


Am 17. Februar 2018 16:08:10 MEZ schrieb Patricia Shanahan <p...@acm.org>:


On 2/17/2018 1:04 AM, Peter kovacs wrote:




+1 A practical demo of what the proposals mean in practice will be

far

more useful than abstract discussion.


How about your Idea to check all Arrays and replace them with

containers?

We would create a master ticket,
Create sub tickets for each case.
Describing what we have to do.
Then distribute the cases and implement it. I try to ask people on

recruitment if they are willing to join.

Maybe this is a good example to try this approach out.

I don't think it is a good example, because it is a long term,
open-ended project.

It would be better to pick something that can be expected to be
completed within a reasonable demonstration period.

---
This email has been checked for viruses by AVG.
http://www.avg.com


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

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




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



Re: [proposal] going Agile

2018-02-17 Thread Peter kovacs
How long should a reasonable demonstration period be?

And what are the success criterias that has to be fulfilled?


Am 17. Februar 2018 16:08:10 MEZ schrieb Patricia Shanahan :
>
>
>On 2/17/2018 1:04 AM, Peter kovacs wrote:
>> 
>> 
>> 
>>> +1 A practical demo of what the proposals mean in practice will be
>far
>>> more useful than abstract discussion.
>>>
>> How about your Idea to check all Arrays and replace them with
>containers?
>> We would create a master ticket,
>> Create sub tickets for each case.
>> Describing what we have to do.
>> Then distribute the cases and implement it. I try to ask people on
>recruitment if they are willing to join.
>> 
>> Maybe this is a good example to try this approach out.
>
>I don't think it is a good example, because it is a long term, 
>open-ended project.
>
>It would be better to pick something that can be expected to be 
>completed within a reasonable demonstration period.
>
>---
>This email has been checked for viruses by AVG.
>http://www.avg.com
>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

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



Re: [proposal] going Agile

2018-02-17 Thread Patricia Shanahan



On 2/17/2018 1:04 AM, Peter kovacs wrote:





+1 A practical demo of what the proposals mean in practice will be far
more useful than abstract discussion.


How about your Idea to check all Arrays and replace them with containers?
We would create a master ticket,
Create sub tickets for each case.
Describing what we have to do.
Then distribute the cases and implement it. I try to ask people on recruitment 
if they are willing to join.

Maybe this is a good example to try this approach out.


I don't think it is a good example, because it is a long term, 
open-ended project.


It would be better to pick something that can be expected to be 
completed within a reasonable demonstration period.


---
This email has been checked for viruses by AVG.
http://www.avg.com


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



Re: [proposal] going Agile

2018-02-17 Thread Peter kovacs



>+1 A practical demo of what the proposals mean in practice will be far 
>more useful than abstract discussion.
>
How about your Idea to check all Arrays and replace them with containers?
We would create a master ticket, 
Create sub tickets for each case.
Describing what we have to do.
Then distribute the cases and implement it. I try to ask people on recruitment 
if they are willing to join.

Maybe this is a good example to try this approach out.

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



Re: [proposal] going Agile

2018-02-16 Thread Patricia Shanahan



On 2/13/2018 2:22 PM, Andrea Pescetti wrote:

Marcus wrote:

@all:
What do you think is the first topic we should start with?


I think the only reasonable way forward is that Peter chooses one of the 
many available tasks (digital signatures? Java 9 support? MSVC update? 
.docx export? you name it) and experiments the workflow limited to it. 
Even if it is a relatively small project, one can decompose it in many 
subtasks: none of these is "too simple" for an experiment.


This way the rest of the project can continue as always, while we have a 
proof of concept that can involve volunteers and so on. Once the proof 
of concept is completed, it can serve as a model for expanding it.


Otherwise my feeling is that we will waste too much time discussing the 
theory and making it perfect, but getting nowhere in practice.


+1 A practical demo of what the proposals mean in practice will be far 
more useful than abstract discussion.


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



Re: [proposal] going Agile

2018-02-13 Thread Andrea Pescetti

Marcus wrote:

@all:
What do you think is the first topic we should start with?


I think the only reasonable way forward is that Peter chooses one of the 
many available tasks (digital signatures? Java 9 support? MSVC update? 
.docx export? you name it) and experiments the workflow limited to it. 
Even if it is a relatively small project, one can decompose it in many 
subtasks: none of these is "too simple" for an experiment.


This way the rest of the project can continue as always, while we have a 
proof of concept that can involve volunteers and so on. Once the proof 
of concept is completed, it can serve as a model for expanding it.


Otherwise my feeling is that we will waste too much time discussing the 
theory and making it perfect, but getting nowhere in practice.


Regards,
  Andrea.

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



Re: [proposal] going Agile

2018-02-13 Thread Marcus

Am 12.02.2018 um 22:15 schrieb Peter Kovacs:

On 10.02.2018 13:26, Marcus wrote:



Therefore let me summarize:

- Use BZ for the development work (e.g, fixing a specific bug).
- Work in Jira for the project tasks and technical coordination (e.g.,
  Windows signing).
- Use Confluence for project work and as documentation base.
- Take the Agile Board functions in Jira if it fits for us.
- Also we can see what we need to do to claim "We are working along
  Kanban rules".

ok, lets try this.


great

However I think we should keep an eye on bandwith needs. That is a good 
point from Damjan. We are not only a first world thing. We are for 
everyone and everyone that is willing should have a chance to participate.
I have seen also in the discussion that we would like to support other 
Open Source Projects if we can. We should therefor concider that Jira is 
only a intermediate solution, to be used until we have a replacement in 
Bugzilla.

Do you agree with my observation?


Sure, we can try to participate in other projects. However, I thing we 
have much to do in our own project.



PS:
I just wantot repeat a sentence from above:

I'm not totally pro or contra your proposal. I just want to express my 
opinion why not everything you've proposed is fitting for us.
My priority is to get a better overview of what needs to be done and 
that we work better together, so we have a better chance in including 
new people.
I will have an eye on topics what volunteers need. I am looking forward 
that we break those eggs one after another together.


I think I did this one wrong, because I started of what I would like to 
do and got into a confrontation role, which I did not want to. Tooling 
and Scrum Framework was not in my center of my goals but It was very 
important in the discussion.
I am a real slow and bad learner. I hope no one takes this personal. I 
am imaptioned. I apologies to myself and to all others for my uttelress 
clumsyness.


Don't worry too much. Many proposals need to be discussed before coming 
to a common understanding - and an agreement.


Thanks for starting this discussion and to try to improve the project 
with new ideas.


I thank you all for the open discussion and the shown courage to speak 
up. I believe that these are values that make us work together. Even 
without Scrum. ;) I hope maybe that others are inspired by this and 
speak up to.

You are all Welcome!


One good thing in Scrum is: fail fast (do something and stop when it's 
not working before wasting more money/time).


So, let's try to implement some ideas and watch closely if it's worth 
the effort.


@all:
What do you think is the first topic we should start with?

Marcus

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



Re: [proposal] going Agile

2018-02-12 Thread Dave Fisher
Hi -

Thanks Peter for driving this topic. I don’t think we all agree, but we can (a) 
try to advance our project organization and (b) acknowledge how we are using 
the many tools we already use.

> On Feb 12, 2018, at 1:15 PM, Peter Kovacs  wrote:
> 
> On 10.02.2018 13:26, Marcus wrote:
> 
>> 
>> Therefore let me summarize:
>> 
>> - Use BZ for the development work (e.g, fixing a specific bug).
>> - Work in Jira for the project tasks and technical coordination (e.g.,
>>   Windows signing).
>> - Use Confluence for project work and as documentation base.
>> - Take the Agile Board functions in Jira if it fits for us.
>> - Also we can see what we need to do to claim "We are working along
>>   Kanban rules".
> ok, lets try this.
> 
> However I think we should keep an eye on bandwith needs. That is a good point 
> from Damjan. We are not only a first world thing. We are for everyone and 
> everyone that is willing should have a chance to participate.
> I have seen also in the discussion that we would like to support other Open 
> Source Projects if we can. We should therefor concider that Jira is only a 
> intermediate solution, to be used until we have a replacement in Bugzilla.
> Do you agree with my observation?

(1) Bug/Issue Trackers available from the ASF.
(a) Bugzilla - OpenOffice has a dedicated instance as does SpamAssassin while 
many projects share a third.
(b) JIRA - Atlassian has provided a free license to the ASF. Not all plugins 
may be available. If one is missing then it will need negotiation.

(2) Wikis available from the ASF.
(a) MediaWiki. This wiki is supported by the AOO PMC and came over as a legacy 
from OpenOffice.org.
(b) Confluence. (Again Atlassian provided free license) This is hosted by the 
ASF and the project has two available for organizing various tasks. We used 
these pretty extensively during migration to organize work.
(c) MoinMoin. Also hosted by the ASF - a more old school wiki. Used by the 
Incubator and others.

> 
>> PS:
>> I just wantot repeat a sentence from above:
>> 
>> I'm not totally pro or contra your proposal. I just want to express my 
>> opinion why not everything you've proposed is fitting for us.
> My priority is to get a better overview of what needs to be done and that we 
> work better together, so we have a better chance in including new people.
> I will have an eye on topics what volunteers need. I am looking forward that 
> we break those eggs one after another together.

My suggestion is to use tools we already have. A wiki seems correct to me. I 
would suggest Confluence, but that is my personal preference. We already have 
tools deployed. I think we just need to manage a table from time to time. 
Periodically we can “Scrum” on dev@ over the status.

> 
> I think I did this one wrong, because I started of what I would like to do 
> and got into a confrontation role, which I did not want to. Tooling and Scrum 
> Framework was not in my center of my goals but It was very important in the 
> discussion.
> I am a real slow and bad learner. I hope no one takes this personal. I am 
> imaptioned. I apologies to myself and to all others for my uttelress 
> clumsyness.

Nothing to forgive since you are proceeding with a rational discussion. So we 
are clear you are looking to have a high/medium level overview of tasks and 
status towards goals. I think this can be a table in a wiki.

> 
> I thank you all for the open discussion and the shown courage to speak up. I 
> believe that these are values that make us work together. Even without Scrum. 
> ;) I hope maybe that others are inspired by this and speak up to.
> You are all Welcome!

Bitte! (Did I use that correctly?)

Regards,
Dave

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



signature.asc
Description: Message signed with OpenPGP


Re: [proposal] going Agile

2018-02-12 Thread Peter Kovacs

On 10.02.2018 13:26, Marcus wrote:



Therefore let me summarize:

- Use BZ for the development work (e.g, fixing a specific bug).
- Work in Jira for the project tasks and technical coordination (e.g.,
  Windows signing).
- Use Confluence for project work and as documentation base.
- Take the Agile Board functions in Jira if it fits for us.
- Also we can see what we need to do to claim "We are working along
  Kanban rules".

ok, lets try this.

However I think we should keep an eye on bandwith needs. That is a good 
point from Damjan. We are not only a first world thing. We are for 
everyone and everyone that is willing should have a chance to participate.
I have seen also in the discussion that we would like to support other 
Open Source Projects if we can. We should therefor concider that Jira is 
only a intermediate solution, to be used until we have a replacement in 
Bugzilla.

Do you agree with my observation?


PS:
I just wantot repeat a sentence from above:

I'm not totally pro or contra your proposal. I just want to express my 
opinion why not everything you've proposed is fitting for us.
My priority is to get a better overview of what needs to be done and 
that we work better together, so we have a better chance in including 
new people.
I will have an eye on topics what volunteers need. I am looking forward 
that we break those eggs one after another together.


I think I did this one wrong, because I started of what I would like to 
do and got into a confrontation role, which I did not want to. Tooling 
and Scrum Framework was not in my center of my goals but It was very 
important in the discussion.
I am a real slow and bad learner. I hope no one takes this personal. I 
am imaptioned. I apologies to myself and to all others for my uttelress 
clumsyness.


I thank you all for the open discussion and the shown courage to speak 
up. I believe that these are values that make us work together. Even 
without Scrum. ;) I hope maybe that others are inspired by this and 
speak up to.

You are all Welcome!

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



Re: [proposal] going Agile

2018-02-11 Thread Peter Kovacs
How can I build only core package?
I am only aware to build everything, or a certain range of modules, or I can 
build explicit one module.

I do not want to take away the ability to build all in one step.
But I think if you are only rebuilding core it saves you a lot of time. And if 
you can check  if there is an effect beyond package boarders, it helps you to 
avoid the issues that had happened in 4.1.5.
Just thinking. I said I am sorry was to hasty in this.

Am 10. Februar 2018 14:46:01 MEZ schrieb Patricia Shanahan :
>
>> On Feb 9, 2018, at 20:05, Peter Kovacs  wrote:
>> 
>>> On 09.02.2018 01:19, Patricia Shanahan wrote:
>>> On February 8, 2018, at 5:51 AM, Peter Kovacs 
>wrote:
>>> 
>>> # Devide the Project into different selfcontained parts. so we have
>>> smaller chunks to swallow. (Maybe we should consider breaking the
>>> compile Process into individual compile steps by package just to
>reduce
>>> Complexity.)
>>> How would this be different from what we have now? The code is
>already divided into modules, and the build process builds each to get
>the packages.
>> I wrote hasty. I do not know for sure since to me the build system is
>a big huge black box.
>> I want more transperency, better control over the code.
>> I think if we hard split the build and only build each package on
>their own we will gain a better view on the code. But I could be wrong.
>> At least I would like to have the option.
>
>You already have the option. I am not sure it would help. 
>
>I am a bit worried be “At least”. Any change that breaks build
>automation would be impractical for me. I need to issue a single
>command, go do none AOO activities, and have my new build ready to test
>when I get back.
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

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



Re: [proposal] going Agile

2018-02-10 Thread Patricia Shanahan

> On Feb 9, 2018, at 20:05, Peter Kovacs  wrote:
> 
>> On 09.02.2018 01:19, Patricia Shanahan wrote:
>> On February 8, 2018, at 5:51 AM, Peter Kovacs  wrote:
>> 
>> # Devide the Project into different selfcontained parts. so we have
>> smaller chunks to swallow. (Maybe we should consider breaking the
>> compile Process into individual compile steps by package just to reduce
>> Complexity.)
>> How would this be different from what we have now? The code is already 
>> divided into modules, and the build process builds each to get the packages.
> I wrote hasty. I do not know for sure since to me the build system is a big 
> huge black box.
> I want more transperency, better control over the code.
> I think if we hard split the build and only build each package on their own 
> we will gain a better view on the code. But I could be wrong.
> At least I would like to have the option.

You already have the option. I am not sure it would help. 

I am a bit worried be “At least”. Any change that breaks build automation would 
be impractical for me. I need to issue a single command, go do none AOO 
activities, and have my new build ready to test when I get back.

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



Re: [proposal] going Agile

2018-02-10 Thread Marcus

Am 10.02.2018 um 07:20 schrieb Peter Kovacs:


On 09.02.2018 23:08, Marcus wrote:

Am 08.02.2018 um 00:32 schrieb Andrea Pescetti:

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.

it depends what you mean with agile.

IMHO forget Scrum as we are not the community to get a commitment for 
this.

Why?


ahm, you should read what I've posted. Then it's getting clear. ;-)


Kanban would be nice.

YAY!
I take this as a success!! :-D
One step forward. Thousands more to go.
So where you would establish the board? - Use trello? Confluence? 
(No ;) )


We use Confluence already, so whay not to continue.


Of course we can also create an ODF, commit to SVN and everybody who 
wants can work on it. We just need to coordinate who and when to commt.



Jira has a Backlog and a Kanban board integrated which I am told are 
very easy to use (Drag & drop I hope...)


I know Jira. But I don't think that it would bring us so many 
advantages. BTW: Drag & Drop is great when you have to move many issues 
quickly to the next status.


Otherwise you can also edit 1-2 fields to change the status. So, I doubt 
that we need this. Therefore a page in Confluence - used as Kanban board 
- will do the same trick.


But there are other key features that could be nice to have (e.g., 
simply the graphically based board "One-Page-Overview".


At the end it's a bit problematic for us with the attributes of 
volunteers, their unpredictable working time (time to work on 
OpenOffice tasks) and the number of volunteers.


BTW:
Above is IMHO why Scrum is not for us. I mean the workflow etc. Of 
course we can be transparent, open, etc. anyway.



You agree?


I don't know if a Product Owner makes sense. Kanban don't know about any 
roles. ;-)


The Product Owner is a single person who tells the team what to do. Then 
the team can decide how to do it.


But I don't want to follow a single person. Why not to decide in the 
team what to do and not to do? Then we can put it into the list (or call 
it Kanban board) and take tasks to work on.


We can organize the work and, sure, one person can volunteer to act as 
"Story/Issue writer" and putting tasks into the right order in Jira and 
its Kanban board. Of course you then can call this person Product Owner. ;-)


Marcus


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



Re: [proposal] going Agile

2018-02-10 Thread Marcus

Am 10.02.2018 um 06:21 schrieb Peter Kovacs:

Migration would be done by infra. They wrote up everything need to know:

https://wiki.apache.org/general/ApacheBugzillaToJiraMigration


I find it cumbersome that all our users should then use Jira to open a 
bug report.


What about to keep Bugzilla for the development work? Damjan has made a 
very valuable point here (rough quote: BZ issues are linked in SVN, 
code, webpages, even Confluence.And nobody wants to migrate this stuff - ).


But then we can use Jira to organize our project work. If you want you 
can then also use the Agile Board functions.


Again, it is not about the tool it is about the workflow. I would like 
to have a Kanbanboard, to get transparency what is worked on, who can I 
approach if I have a volunteer to work together. New Volunteers need 
someone they can follow.


I want to have a Backlog to define what is important to do next, and to 
fill the detailed steps together what we need to do. Maybe we could 
together fill out so much detail, that it is easy for everyone to start 
on the topic.



That is the original proposal. I know that Jira is _the_ industry tool 
to this. Every major professional major Project uses Jira. It would not 
be so popular if it would not have a certain quality.


Yes, but we are not "industry" and also not "professional". Did you know 
that it is closed source and you need to pay for to be able to use it? 
;-) Luckily the ASF got a license free of charge.


I know that you complained onec there are so many differnt links to note 
and tools that we have in our arsenal.


I don't complain. I just want to express my opinion why not everything 
you've proposed is fitting for us.



Jira could be reduce the lot. Thats why I think it is convenient.


BTW. If we start using Kanban, I will reach out to the one Volunteer who 
volunteered and loves Kanban if want to have a try with us, we are now 
following his way (more or less...) Maybe he jumps at it.


And that's the point: maybe. We simple don't know if we get more 
volunteers (that will also stay).


Thats the nature of volunteers. They will look if they like what they 
see and are gone when they are no longer committed. It's great when we 
get feedback what should be changed, so that they show a higher 
commitment or simply stay longer.


We had another Volunteer who said: tell me what to do I do it. But I do 
not have the interest to figure it out on my own. We can currently not 
use these people. With Backlog and Board we can.


Sure, these people can help us to go further. With our without a 
graphical based board. Sure, it's easier with it.


Of course we can change some workflows. But I doubt that it would bring 
us more volunteers when we turn everything inside out.


Therefore let me summarize:

- Use BZ for the development work (e.g, fixing a specific bug).
- Work in Jira for the project tasks and technical coordination (e.g.,
  Windows signing).
- Use Confluence for project work and as documentation base.
- Take the Agile Board functions in Jira if it fits for us.
- Also we can see what we need to do to claim "We are working along
  Kanban rules".

PS:
I just wantot repeat a sentence from above:

I'm not totally pro or contra your proposal. I just want to express my 
opinion why not everything you've proposed is fitting for us.


Marcus




On 09.02.2018 23:05, Marcus wrote:
I would prefer to avoid the upheaval of switching to a different 
issue tracker if at all possible.


+1

Jira is just another tool that wouldn't bring us any nearer to closed 
issues. BTW, start new? Then you would trash all old issues which 
isn't a good thing. Move them over to Jira? Great, who is the 
volunteer to do the migration? ;-)


But Confluence can bring us some overview. We can structure similar BZ 
issues to packages and then we can work on them. 



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



Re: [proposal] going Agile

2018-02-10 Thread Damjan Jovanovic
On Sat, Feb 10, 2018 at 12:05 AM, Marcus <marcus.m...@wtnet.de> wrote:

> Am 09.02.2018 um 01:19 schrieb Patricia Shanahan:
>
>> On February 8, 2018, at 5:51 AM, Peter Kovacs <pe...@apache.org> wrote:
>>
>> # Start spreading knowledge in our development team.
>>>
>>>>
>>>> 1) I would like to propose a Product Backlog / OIL (OpenIssue) List
>>>>> to priorize Issues we need to work on. The most Valueable item comes
>>>>> to the top, the least to the bottom. What Value exactly is is up to
>>>>> discussion.
>>>>>
>>>>
>>>> Theoretically, we have a list of issues in Bugzilla with target 4.2.0.
>>>> Validating them all and/or setting targets will basically give you
>>>> what you wish. I think Bugzilla has some concept of an issue weight
>>>> that would more or less allow to prioritize issues with the current
>>>> tooling, so this can be done. At least, once we agree on list on a
>>>> series of "must-haves" for 4.2.0, these could be turned into something
>>>> similar to your backlog.
>>>>
>>> Maybe we should not discuss tooling now. I think in the end it has to
>>> work. Jira is mostly a convenient choice. But we can think of all other
>>> sort of combinations. (However we have already a lot of Tools.So I would
>>> rather try to reduce those. We can try Bugzilla, but i do not want to
>>> start modifying Bugzilla in order to get what we need.
>>>
>>
>> I would prefer to avoid the upheaval of switching to a different issue
>> tracker if at all possible.
>>
>
> +1
>
> Jira is just another tool that wouldn't bring us any nearer to closed
> issues. BTW, start new? Then you would trash all old issues which isn't a
> good thing. Move them over to Jira? Great, who is the volunteer to do the
> migration? ;-)
>
>
>
+1 to that. We have Bugzilla bug numbers in SVN and even in the code, and
links to Bugzilla URLs in places too, who is going to find and replace all
of those?

I also find Bugzilla much faster to work with and lighter on the network
(not everyone is in a 1st world country).

Damjan


Re: [proposal] going Agile

2018-02-10 Thread Patricia Shanahan
Openness can be a real problem. I have mainly done security fixes that had to 
stay on the private lists until released and disclosed. 

Patricia

> On Feb 10, 2018, at 06:20, Peter Kovacs  wrote:
> 
> 
>> On 09.02.2018 23:08, Marcus wrote:
>>> Am 08.02.2018 um 00:32 schrieb Andrea Pescetti:
>>> Peter Kovacs wrote:
 I would like to propose that we apply Agile development methods as much as 
 we can.
>> it depends what you mean with agile.
>> 
>> IMHO forget Scrum as we are not the community to get a commitment for this.
> Why? What does our community do not like about scrum?
> We do not like the Values of scrum?
> Focus
> Openess
> Respect
> Commitment
> Courage
> 
> Or maybe we do not like the pillars?
> Transparency, Inspect and adapt?
> ;)
> 
> Agreed, I think we can not use SCRUM in the same way Companies do, too. But I 
> think we can use the Idea of scrum to work together and to simplify our work. 
> What would you use to make our work simple?
> Why do you think Ordering our Bugs in a List and add details to them will not 
> bring us forward?
>> 
>> Kanban would be nice.
> YAY!
> I take this as a success!! :-D
> One step forward. Thousands more to go.
> So where you would establish the board? - Use trello? Confluence? (No 
> ;) )
> Jira has a Backlog and a Kanban board integrated which I am told are very 
> easy to use (Drag & drop I hope...)
>> 
>> At the end it's a bit problematic for us with the attributes of volunteers, 
>> their unpredictable working time (time to work on OpenOffice tasks) and the 
>> number of volunteers.
>> 
>> However, we should try to keep it simple as Product Backlop, Product Owner, 
>> Tasks, Sub-Tasks, Jira, Confluence etc. would be much too much complexity 
>> for us when doing/using all of them.
> Maybe I have learned a total different scrum then you did? - Agile does not 
> mean to use everything like a fixed ruleset. To me SCRUM is a template to 
> start with It just tells us what prooved to be working well. But How and what 
> we can use from the framework, is up to us.
> 
> Again. Only Product Backlog, Product Owner, and a Kanban board are on the 
> table as to be used. And I do only want the Product owner so we have some 
> steward for the list. I am totaly fine with a Release Manager looking into it.
> I have not explained to maximize Value and Output, since I do not believe we 
> do need to maximize Value and Output, since we are Open Source Volunteering 
> Community and not OpenSource Commercial Product. Small but important 
> difference not to forget. (If we get OpenSource Comercial part, we have to 
> make sure they can spend their energy on maximizing Value. ;) )
> 
> You agree?
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

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



Re: [proposal] going Agile

2018-02-09 Thread Peter Kovacs


On 09.02.2018 23:08, Marcus wrote:

Am 08.02.2018 um 00:32 schrieb Andrea Pescetti:

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.

it depends what you mean with agile.

IMHO forget Scrum as we are not the community to get a commitment for 
this.

Why? What does our community do not like about scrum?
We do not like the Values of scrum?
Focus
Openess
Respect
Commitment
Courage

Or maybe we do not like the pillars?
Transparency, Inspect and adapt?
;)

Agreed, I think we can not use SCRUM in the same way Companies do, too. 
But I think we can use the Idea of scrum to work together and to 
simplify our work. What would you use to make our work simple?
Why do you think Ordering our Bugs in a List and add details to them 
will not bring us forward?


Kanban would be nice.

YAY!
I take this as a success!! :-D
One step forward. Thousands more to go.
So where you would establish the board? - Use trello? Confluence? 
(No ;) )
Jira has a Backlog and a Kanban board integrated which I am told are 
very easy to use (Drag & drop I hope...)


At the end it's a bit problematic for us with the attributes of 
volunteers, their unpredictable working time (time to work on 
OpenOffice tasks) and the number of volunteers.


However, we should try to keep it simple as Product Backlop, Product 
Owner, Tasks, Sub-Tasks, Jira, Confluence etc. would be much too much 
complexity for us when doing/using all of them.
Maybe I have learned a total different scrum then you did? - Agile does 
not mean to use everything like a fixed ruleset. To me SCRUM is a 
template to start with It just tells us what prooved to be working well. 
But How and what we can use from the framework, is up to us.


Again. Only Product Backlog, Product Owner, and a Kanban board are on 
the table as to be used. And I do only want the Product owner so we have 
some steward for the list. I am totaly fine with a Release Manager 
looking into it.
I have not explained to maximize Value and Output, since I do not 
believe we do need to maximize Value and Output, since we are Open 
Source Volunteering Community and not OpenSource Commercial Product. 
Small but important difference not to forget. (If we get OpenSource 
Comercial part, we have to make sure they can spend their energy on 
maximizing Value. ;) )


You agree?

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



Re: [proposal] going Agile

2018-02-09 Thread Peter Kovacs

Migration would be done by infra. They wrote up everything need to know:

https://wiki.apache.org/general/ApacheBugzillaToJiraMigration


Again, it is not about the tool it is about the workflow. I would like 
to have a Kanbanboard, to get transparency what is worked on, who can I 
approach if I have a volunteer to work together. New Volunteers need 
someone they can follow.


I want to have a Backlog to define what is important to do next, and to 
fill the detailed steps together what we need to do. Maybe we could 
together fill out so much detail, that it is easy for everyone to start 
on the topic.



That is the original proposal. I know that Jira is _the_ industry tool 
to this. Every major professional major Project uses Jira. It would not 
be so popular if it would not have a certain quality.


I know that you complained onec there are so many differnt links to note 
and tools that we have in our arsenal.


Jira could be reduce the lot. Thats why I think it is convenient.


BTW. If we start using Kanban, I will reach out to the one Volunteer who 
volunteered and loves Kanban if want to have a try with us, we are now 
following his way (more or less...) Maybe he jumps at it.


We had another Volunteer who said: tell me what to do I do it. But I do 
not have the interest to figure it out on my own. We can currently not 
use these people. With Backlog and Board we can.


That would mean 2 more developers. Propably. Maybe they quick because it 
is frustrating to build OpenOffice. *ROFL*




On 09.02.2018 23:05, Marcus wrote:
I would prefer to avoid the upheaval of switching to a different 
issue tracker if at all possible.


+1

Jira is just another tool that wouldn't bring us any nearer to closed 
issues. BTW, start new? Then you would trash all old issues which 
isn't a good thing. Move them over to Jira? Great, who is the 
volunteer to do the migration? ;-)


But Confluence can bring us some overview. We can structure similar BZ 
issues to packages and then we can work on them. 




Re: [proposal] going Agile

2018-02-09 Thread Marcus

Am 08.02.2018 um 00:32 schrieb Andrea Pescetti:

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.


it depends what you mean with agile.

IMHO forget Scrum as we are not the community to get a commitment for this.

Kanban would be nice.

At the end it's a bit problematic for us with the attributes of 
volunteers, their unpredictable working time (time to work on OpenOffice 
tasks) and the number of volunteers.


However, we should try to keep it simple as Product Backlop, Product 
Owner, Tasks, Sub-Tasks, Jira, Confluence etc. would be much too much 
complexity for us when doing/using all of them.


My 2 ct.
(also with my years of experience as Scrum Product Owner)

Marcus


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



Re: [proposal] going Agile

2018-02-09 Thread Marcus

Am 09.02.2018 um 01:19 schrieb Patricia Shanahan:

On February 8, 2018, at 5:51 AM, Peter Kovacs  wrote:


# Start spreading knowledge in our development team.



1) I would like to propose a Product Backlog / OIL (OpenIssue) List
to priorize Issues we need to work on. The most Valueable item comes
to the top, the least to the bottom. What Value exactly is is up to
discussion.


Theoretically, we have a list of issues in Bugzilla with target 4.2.0.
Validating them all and/or setting targets will basically give you
what you wish. I think Bugzilla has some concept of an issue weight
that would more or less allow to prioritize issues with the current
tooling, so this can be done. At least, once we agree on list on a
series of "must-haves" for 4.2.0, these could be turned into something
similar to your backlog.

Maybe we should not discuss tooling now. I think in the end it has to
work. Jira is mostly a convenient choice. But we can think of all other
sort of combinations. (However we have already a lot of Tools.So I would
rather try to reduce those. We can try Bugzilla, but i do not want to
start modifying Bugzilla in order to get what we need.


I would prefer to avoid the upheaval of switching to a different issue tracker 
if at all possible.


+1

Jira is just another tool that wouldn't bring us any nearer to closed 
issues. BTW, start new? Then you would trash all old issues which isn't 
a good thing. Move them over to Jira? Great, who is the volunteer to do 
the migration? ;-)


But Confluence can bring us some overview. We can structure similar BZ 
issues to packages and then we can work on them.


Marcus


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



Re: [proposal] going Agile

2018-02-09 Thread Peter Kovacs

On 09.02.2018 01:19, Patricia Shanahan wrote:

On February 8, 2018, at 5:51 AM, Peter Kovacs  wrote:

# Devide the Project into different selfcontained parts. so we have
smaller chunks to swallow. (Maybe we should consider breaking the
compile Process into individual compile steps by package just to reduce
Complexity.)
How would this be different from what we have now? The code is already divided 
into modules, and the build process builds each to get the packages.
I wrote hasty. I do not know for sure since to me the build system is a 
big huge black box.

I want more transperency, better control over the code.
I think if we hard split the build and only build each package on their 
own we will gain a better view on the code. But I could be wrong.

At least I would like to have the option.

# Start spreading knowledge in our development team.
Maybe we should not discuss tooling now. I think in the end it has to
work. Jira is mostly a convenient choice. But we can think of all other
sort of combinations. (However we have already a lot of Tools.So I would
rather try to reduce those. We can try Bugzilla, but i do not want to
start modifying Bugzilla in order to get what we need.

I would prefer to avoid the upheaval of switching to a different issue tracker 
if at all possible.
The tool is not important. It is just a tool that has to serve a 
purpose. Important to me is that we change the method we work.

In my opinion, YAGNI is just as important for process design as for software 
design.
Thats the principle of lean management. In my opinion we currently work 
on this method, but keep the PMO structure that the the project was 
build on from the old days. And thats makeing it all difficult for everyone.

If we get to the point of having enough active volunteers that we need to think 
in terms of forming teams we will know a lot more about their skills, 
availability etc. and therefore be able to do a better job of organizing those 
teams.
We had 4 or 5 candidates. So far no one stayed. They had a look and went 
off. You can blame all sorts of things. In reality you have only control 
over one thing that is you. We do only have the power to change this 
project.

If we want that people stay, we need to change. Not other way round.

The question is how we want to change.
I like the family trait we have. I would like to use this trait to make 
people stay. Agile teams in my eyes will open a gate for new people into 
our community. They start learning some people from the community 
quickly and as they work they learn more. Becomming more attached. Thats 
why I am suggesting it.


What would you change with the ressources we have to make people stay?

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



Re: [proposal] going Agile

2018-02-08 Thread Patricia Shanahan
On February 8, 2018, at 5:51 AM, Peter Kovacs  wrote:

>Thank you these are good points.
>On 08.02.2018 00:32, Andrea Pescetti wrote:
>> Peter Kovacs wrote:
>>> I would like to propose that we apply Agile development methods as 
>>> much as we can.
>>
>> Well, "as much as we can" is the key here. OpenOffice is as agile as 
>> an elephant. A lot of us use Agile in their daily work activities, and 
>> maybe they even like it, but it's a totally different vision from the 
>> Apache/OpenOffice way.
>I agree. But I am proposeing to reorganize the project so we do not deal 
>with the Elefant size we bring from history.
>I want
># Core Tasks are done in teams, to releave the commitment on the 
>individual volunteer
># Devide the Project into different selfcontained parts. so we have 
>smaller chunks to swallow. (Maybe we should consider breaking the 
>compile Process into individual compile steps by package just to reduce 
>Complexity.)

How would this be different from what we have now? The code is already divided 
into modules, and the build process builds each to get the packages.


># Start spreading knowledge in our development team.
>>
>>> 1) I would like to propose a Product Backlog / OIL (OpenIssue) List 
>>> to priorize Issues we need to work on. The most Valueable item comes 
>>> to the top, the least to the bottom. What Value exactly is is up to 
>>> discussion.
>>
>> Theoretically, we have a list of issues in Bugzilla with target 4.2.0. 
>> Validating them all and/or setting targets will basically give you 
>> what you wish. I think Bugzilla has some concept of an issue weight 
>> that would more or less allow to prioritize issues with the current 
>> tooling, so this can be done. At least, once we agree on list on a 
>> series of "must-haves" for 4.2.0, these could be turned into something 
>> similar to your backlog.
>Maybe we should not discuss tooling now. I think in the end it has to 
>work. Jira is mostly a convenient choice. But we can think of all other 
>sort of combinations. (However we have already a lot of Tools.So I would 
>rather try to reduce those. We can try Bugzilla, but i do not want to 
>start modifying Bugzilla in order to get what we need.

I would prefer to avoid the upheaval of switching to a different issue tracker 
if at all possible.


>>
>>> 2) I would further propose that we create a new Role - The Product 
>>> Owner.
>>
>> This is the Release Manager and the community. If someone steps us to 
>> do the "secretarial" work of maintaining issues, you have your 
>> volunteer; giving him a title is something we normally don't do, but 
>> this is irrelevant.
>yea, we can do so if all are fine by this.
>>
>>> 3) If we agree on the Backlist I further suggest that we open up a 
>>> Jira Issue Tracker.
>>> We can keep the Bugzilla Bugtracker for tracking the bugs, and create 
>>> Issues from it. Or we move to Jira completly.
>>> Why do I propose the tool change? Because We can track with Jira 
>>> Issues, have the Backlog and can use a Project wide Kanban board 
>>> (replacing in part the Sprints from Scrum) to track Which activity 
>>> has been started. Where we can create Teams.
>>
>> This won't work. This is tooling that I'm used to using every day, so 
>> mine is not a resistance to change. Just, it's clear that nobody does 
>> OpenOffice as his day job, so we can't count on being able to assign 
>> an issue to someone for example, or on having an issue handled within 
>> a certain "sprint". At most, we can hope that people will voluntarily 
>> do a very occasional "scrum" like I do for the localization stuff, 
>> reporting here when I have some time to work on it and saying where 
>> I'm stuck and what would be the next step. The rest looks unrealistic.
>Let me try to describe the way I think we could make it work.
>We form the Core teams. A Core team does consist at least of 1 PMC 
>(which can take another Role), 2 Programmer and 2 QA Volunteers and is 
>limited at a maximum of 9 People. Each team is working together and 
>picks Topics from the Backlog in their TeamBacklog of what they believe 
>they can handle within the next month (Just to have a limitation on 
>tasks, but we could also limit as Kanban does it by a fix amount lets 
>say 3 Items). We do setup a Team List for each team. There they can have 
>their "meetings" on weekend each memebr posts a Standupmail, which 
>contains the availability. If he is stuck with issues somewhere. And 
>maybe if he is on track or not. (Transperency, Inspection and 
>Adaptaition are the important Buzzwords here)
>What does a Core team look into?
># Security Bugs would be a candidate. Not all Teammembers need to be on 
>the list thought.
># Dependency Migration
># Core Code Changes
># important Bugfixes (i.e. Crashes)
>What not?
># new Features
># nice to have
># tooling (except we define something as critical and must have.)

In my opinion, YAGNI is just as important for process design as for software 
design. If we 

Re: [proposal] going Agile

2018-02-07 Thread DurgaPrasad Potnuru
+1
I am in favor, and like the way duscussions are heading. Willing to
contribute in setting up project in Jira if thus goes through

On Feb 8, 2018 11:21, "Peter Kovacs"  wrote:

> Thank you these are good points.
>
> On 08.02.2018 00:32, Andrea Pescetti wrote:
>
>> Peter Kovacs wrote:
>>
>>> I would like to propose that we apply Agile development methods as much
>>> as we can.
>>>
>>
>> Well, "as much as we can" is the key here. OpenOffice is as agile as an
>> elephant. A lot of us use Agile in their daily work activities, and maybe
>> they even like it, but it's a totally different vision from the
>> Apache/OpenOffice way.
>>
> I agree. But I am proposeing to reorganize the project so we do not deal
> with the Elefant size we bring from history.
> I want
> # Core Tasks are done in teams, to releave the commitment on the
> individual volunteer
> # Devide the Project into different selfcontained parts. so we have
> smaller chunks to swallow. (Maybe we should consider breaking the compile
> Process into individual compile steps by package just to reduce Complexity.)
> # Start spreading knowledge in our development team.
>
>>
>> 1) I would like to propose a Product Backlog / OIL (OpenIssue) List to
>>> priorize Issues we need to work on. The most Valueable item comes to the
>>> top, the least to the bottom. What Value exactly is is up to discussion.
>>>
>>
>> Theoretically, we have a list of issues in Bugzilla with target 4.2.0.
>> Validating them all and/or setting targets will basically give you what you
>> wish. I think Bugzilla has some concept of an issue weight that would more
>> or less allow to prioritize issues with the current tooling, so this can be
>> done. At least, once we agree on list on a series of "must-haves" for
>> 4.2.0, these could be turned into something similar to your backlog.
>>
> Maybe we should not discuss tooling now. I think in the end it has to
> work. Jira is mostly a convenient choice. But we can think of all other
> sort of combinations. (However we have already a lot of Tools.So I would
> rather try to reduce those. We can try Bugzilla, but i do not want to start
> modifying Bugzilla in order to get what we need.
>
>>
>> 2) I would further propose that we create a new Role - The Product Owner.
>>>
>>
>> This is the Release Manager and the community. If someone steps us to do
>> the "secretarial" work of maintaining issues, you have your volunteer;
>> giving him a title is something we normally don't do, but this is
>> irrelevant.
>>
> yea, we can do so if all are fine by this.
>
>>
>> 3) If we agree on the Backlist I further suggest that we open up a Jira
>>> Issue Tracker.
>>> We can keep the Bugzilla Bugtracker for tracking the bugs, and create
>>> Issues from it. Or we move to Jira completly.
>>> Why do I propose the tool change? Because We can track with Jira Issues,
>>> have the Backlog and can use a Project wide Kanban board (replacing in part
>>> the Sprints from Scrum) to track Which activity has been started. Where we
>>> can create Teams.
>>>
>>
>> This won't work. This is tooling that I'm used to using every day, so
>> mine is not a resistance to change. Just, it's clear that nobody does
>> OpenOffice as his day job, so we can't count on being able to assign an
>> issue to someone for example, or on having an issue handled within a
>> certain "sprint". At most, we can hope that people will voluntarily do a
>> very occasional "scrum" like I do for the localization stuff, reporting
>> here when I have some time to work on it and saying where I'm stuck and
>> what would be the next step. The rest looks unrealistic.
>>
> Let me try to describe the way I think we could make it work.
>
> We form the Core teams. A Core team does consist at least of 1 PMC (which
> can take another Role), 2 Programmer and 2 QA Volunteers and is limited at
> a maximum of 9 People. Each team is working together and picks Topics from
> the Backlog in their TeamBacklog of what they believe they can handle
> within the next month (Just to have a limitation on tasks, but we could
> also limit as Kanban does it by a fix amount lets say 3 Items). We do setup
> a Team List for each team. There they can have their "meetings" on weekend
> each memebr posts a Standupmail, which contains the availability. If he is
> stuck with issues somewhere. And maybe if he is on track or not.
> (Transperency, Inspection and Adaptaition are the important Buzzwords here)
>
> What does a Core team look into?
> # Security Bugs would be a candidate. Not all Teammembers need to be on
> the list thought.
> # Dependency Migration
> # Core Code Changes
> # important Bugfixes (i.e. Crashes)
>
> What not?
> # new Features
> # nice to have
> # tooling (except we define something as critical and must have.)
>
> I would not change language list, or other activities. However if we have
> a backlog we could put other stuff there. Like the merchendise Topics.
> Those are then a free for all volunteers to care 

Re: [proposal] going Agile

2018-02-07 Thread Peter Kovacs

Thank you these are good points.

On 08.02.2018 00:32, Andrea Pescetti wrote:

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.


Well, "as much as we can" is the key here. OpenOffice is as agile as 
an elephant. A lot of us use Agile in their daily work activities, and 
maybe they even like it, but it's a totally different vision from the 
Apache/OpenOffice way.
I agree. But I am proposeing to reorganize the project so we do not deal 
with the Elefant size we bring from history.

I want
# Core Tasks are done in teams, to releave the commitment on the 
individual volunteer
# Devide the Project into different selfcontained parts. so we have 
smaller chunks to swallow. (Maybe we should consider breaking the 
compile Process into individual compile steps by package just to reduce 
Complexity.)

# Start spreading knowledge in our development team.


1) I would like to propose a Product Backlog / OIL (OpenIssue) List 
to priorize Issues we need to work on. The most Valueable item comes 
to the top, the least to the bottom. What Value exactly is is up to 
discussion.


Theoretically, we have a list of issues in Bugzilla with target 4.2.0. 
Validating them all and/or setting targets will basically give you 
what you wish. I think Bugzilla has some concept of an issue weight 
that would more or less allow to prioritize issues with the current 
tooling, so this can be done. At least, once we agree on list on a 
series of "must-haves" for 4.2.0, these could be turned into something 
similar to your backlog.
Maybe we should not discuss tooling now. I think in the end it has to 
work. Jira is mostly a convenient choice. But we can think of all other 
sort of combinations. (However we have already a lot of Tools.So I would 
rather try to reduce those. We can try Bugzilla, but i do not want to 
start modifying Bugzilla in order to get what we need.


2) I would further propose that we create a new Role - The Product 
Owner.


This is the Release Manager and the community. If someone steps us to 
do the "secretarial" work of maintaining issues, you have your 
volunteer; giving him a title is something we normally don't do, but 
this is irrelevant.

yea, we can do so if all are fine by this.


3) If we agree on the Backlist I further suggest that we open up a 
Jira Issue Tracker.
We can keep the Bugzilla Bugtracker for tracking the bugs, and create 
Issues from it. Or we move to Jira completly.
Why do I propose the tool change? Because We can track with Jira 
Issues, have the Backlog and can use a Project wide Kanban board 
(replacing in part the Sprints from Scrum) to track Which activity 
has been started. Where we can create Teams.


This won't work. This is tooling that I'm used to using every day, so 
mine is not a resistance to change. Just, it's clear that nobody does 
OpenOffice as his day job, so we can't count on being able to assign 
an issue to someone for example, or on having an issue handled within 
a certain "sprint". At most, we can hope that people will voluntarily 
do a very occasional "scrum" like I do for the localization stuff, 
reporting here when I have some time to work on it and saying where 
I'm stuck and what would be the next step. The rest looks unrealistic.

Let me try to describe the way I think we could make it work.

We form the Core teams. A Core team does consist at least of 1 PMC 
(which can take another Role), 2 Programmer and 2 QA Volunteers and is 
limited at a maximum of 9 People. Each team is working together and 
picks Topics from the Backlog in their TeamBacklog of what they believe 
they can handle within the next month (Just to have a limitation on 
tasks, but we could also limit as Kanban does it by a fix amount lets 
say 3 Items). We do setup a Team List for each team. There they can have 
their "meetings" on weekend each memebr posts a Standupmail, which 
contains the availability. If he is stuck with issues somewhere. And 
maybe if he is on track or not. (Transperency, Inspection and 
Adaptaition are the important Buzzwords here)


What does a Core team look into?
# Security Bugs would be a candidate. Not all Teammembers need to be on 
the list thought.

# Dependency Migration
# Core Code Changes
# important Bugfixes (i.e. Crashes)

What not?
# new Features
# nice to have
# tooling (except we define something as critical and must have.)

I would not change language list, or other activities. However if we 
have a backlog we could put other stuff there. Like the merchendise 
Topics. Those are then a free for all volunteers to care in their time.


That is the setup I  could imagine that could work. Please note setting 
up the Backlog is a lot of work, because we need to setup the Log in a 
way that everyone with the right skillset does understand exactly what 
to do for this task. You will quickly see thats not always easy. 
Especially in the beginning.


I think with that we have a rough structure we can operate on. 

Re: [proposal] going Agile

2018-02-07 Thread Andrea Pescetti

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.


Well, "as much as we can" is the key here. OpenOffice is as agile as an 
elephant. A lot of us use Agile in their daily work activities, and 
maybe they even like it, but it's a totally different vision from the 
Apache/OpenOffice way.


1) I would like to propose a Product Backlog / OIL (OpenIssue) List to 
priorize Issues we need to work on. The most Valueable item comes to the 
top, the least to the bottom. What Value exactly is is up to discussion.


Theoretically, we have a list of issues in Bugzilla with target 4.2.0. 
Validating them all and/or setting targets will basically give you what 
you wish. I think Bugzilla has some concept of an issue weight that 
would more or less allow to prioritize issues with the current tooling, 
so this can be done. At least, once we agree on list on a series of 
"must-haves" for 4.2.0, these could be turned into something similar to 
your backlog.



2) I would further propose that we create a new Role - The Product Owner.


This is the Release Manager and the community. If someone steps us to do 
the "secretarial" work of maintaining issues, you have your volunteer; 
giving him a title is something we normally don't do, but this is 
irrelevant.


3) If we agree on the Backlist I further suggest that we open up a Jira 
Issue Tracker.
We can keep the Bugzilla Bugtracker for tracking the bugs, and create 
Issues from it. Or we move to Jira completly.
Why do I propose the tool change? Because We can track with Jira Issues, 
have the Backlog and can use a Project wide Kanban board (replacing in 
part the Sprints from Scrum) to track Which activity has been started. 
Where we can create Teams.


This won't work. This is tooling that I'm used to using every day, so 
mine is not a resistance to change. Just, it's clear that nobody does 
OpenOffice as his day job, so we can't count on being able to assign an 
issue to someone for example, or on having an issue handled within a 
certain "sprint". At most, we can hope that people will voluntarily do a 
very occasional "scrum" like I do for the localization stuff, reporting 
here when I have some time to work on it and saying where I'm stuck and 
what would be the next step. The rest looks unrealistic.


if someone wants to stay independant, thats fine. I support that. 
Freedom is all we want after all. Do you agree?


I think it's not about a desire to stay independent, but the necessity 
to avoid too much structure (despite the name, Agile is a structure, and 
a very very heavy one). We simply can't afford it. Then, if someone 
wants to be a volunteer and maintain (in whatever way; Kanban boards are 
nice, but you don't need JIRA for that; there's plenty of tools for it) 
something that can visually give the idea of where we are for 4.2.0, 
I'll be happy with that. And even with calling her the "Product Owner" 
if she wishes. The impossible thing is to impose a structure on a group 
like us that has scarce and unpredictable availability, and where people 
can't just be assigned a task, and where we need community consensus for 
decisions.


Regards,
  Andrea.

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



[proposal] going Agile

2018-02-07 Thread Peter Kovacs

Hello all,

 - I would like to propose that we apply Agile development methods as 
much as we can. For start we need clarity what task are the most 
pressing ones.


 1) I would like to propose a Product Backlog / OIL (OpenIssue) List to 
priorize Issues we need to work on. The most Valueable item comes to the 
top, the least to the bottom. What Value exactly is is up to discussion.


2) I would further propose that we create a new Role - The Product Owner.

The Task of the Product owner is to look that that the Backlog is 
maintained. That the Team does understand the issues or Questions are 
clarified.


He decides in doubt on the Value of an item. He is not the one who 
writes the list. This is our all task.


3) If we agree on the Backlist I further suggest that we open up a Jira 
Issue Tracker.


We can keep the Bugzilla Bugtracker for tracking the bugs, and create 
Issues from it. Or we move to Jira completly.


Why do I propose the tool change? Because We can track with Jira Issues, 
have the Backlog and can use a Project wide Kanban board (replacing in 
part the Sprints from Scrum) to track Which activity has been started. 
Where we can create Teams.



The hope is that we can gain focus. Even build teams, where more 
experienced work with less experience, distribute knowledge by 
cooperation. And the hope is that we can guide people.


If you have Questions or did not understand something then please ask. 
From Agile Perspective Development is not a thing that Programmers do 
but a lot more people. And I would like that testers, Dokumenters and 
all other people who whish to work together understand what this about 
how it works.



However I want at the same time no one to pull out of his comfort Zone. 
if someone wants to stay independant, thats fine. I support that. 
Freedom is all we want after all.


Do you agree?

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



Re: procedure for going from RC to release

2016-04-04 Thread Carl Marcum

On 04/03/2016 06:17 PM, Marcus wrote:

Am 04/03/2016 09:42 PM, schrieb Andrea Pescetti:

Carl Marcum wrote:

I was looking at how some other projects handled "extras" things like
this.


Other projects designed their trees in a different way.


I found Maven uses sub-folders under release/maven for plugins,
plugin-tools, etc, that don't go into their main release folder. [1].


Well, here the issue is: we have assumed so far that the OpenOffice
project releases, well, OpenOffice. This will still be true, but about
one user in ten millions will want the NetBeans plugin. We can't make
things more complex for the other 99,9% of users due to this.

So for example, one thing we can't do is to partition (now) our
"openoffice" tree into "releases" (for the "real" releases) and
"devtools". If we had known this years ago, it would have made sense
even with the large difference in numbers.

In other words: I would consider
https://dist.apache.org/repos/dist/release/openoffice
to be taken. There will be no "releases" subfolder created in it, to
avoid large management costs for something 99,9% of users won't use.
Either we go for the dirty solution you advocate, where we mix release
numbers and the "devtools" folder (which I don't like, but this is also
not worth a long discussion honestly), or you place the plugin sources
in some existing place.


Should we use something like a devtools subfolder under
release/openoffice so they don't have to be redone for each maintenance
release of AOO or end up with multiples in each AOO release?


Multiple? You will want to look up the distinction between dist and
archive. If you don't find the relevant documentation, just ask and I'll
dig it up from the website.


https://dist.apache.org/repos/dist/release/openoffice/devtools/


I don't know how going for the "dirty" solution will affect scripts. It
will surely result in misaligned trees in dist/ and SourceForge but this
is not particularly problematic. If I recall correctly the download page
options are populated via JS, but in turn that JS is probably generated
(by Marcus?) based on some tree inspection; so this would need a check
too, to ensure the extra "devtools" directory doesn't get in the way.

On the other hand, the extra "devtools" folder will be ugly, but it will
provide a container for all releases that are not related to our "main"
product.

We could at least agree that http://www.openoffice.org/download/ won't
change at all with the plugin release, right?


of course. As you wrote correctly 99% of our users will not use the 
plugin. And the remaining 1% are no users but devs. And these people 
will use it directly from Netbeans anyway. ;-)


So, I would see releasing the plugin as a part of the open source 
promise: Everybody can have a look into the source code to see what is 
going on - if they like to do it.


Sure, I can implement also this pckage into the JS download scriping 
and provide something on the download page. However, I really doubt 
that it is worth the effort. ;-)


OK seriously, Carl:
- You can do whatever you see fit to release the source package 
regarding filenames, directory structure or where to put it in the 
tree on SourceForge. It will not influence the other AOO download 
behavior.
Adding it in the "source/" dir along with the other files is OK. Or 
create a new "devtools/" dir.


- When you have some documentation ready or just in mind, don't forget 
to mention this source package incl. a link. Then we can proof that it 
is available as open source.


- As far as I've understood, the important part is the binary at 
Netbeans.org, right? Then we should keep the effort on openoffice.org 
as low as possible as it is just for 1%.


- And, finally, when we see that something was done wrong. OK, then 
let's fix it at the lastest with the next plugin release.


My 2 ct.

Marcus




Hi Marcus,

Yes all these are source only. The binaries for the netbeans integration 
will be from netbeans.org and the bootstrap-connector and groovy UNO are 
Maven repo.


Thanks,
Carl

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



Re: procedure for going from RC to release

2016-04-03 Thread Marcus

Am 04/03/2016 10:10 PM, schrieb Carl Marcum:

On 04/03/2016 03:42 PM, Andrea Pescetti wrote:

Carl Marcum wrote:

I was looking at how some other projects handled "extras" things like
this.


Other projects designed their trees in a different way.


I found Maven uses sub-folders under release/maven for plugins,
plugin-tools, etc, that don't go into their main release folder. [1].


Well, here the issue is: we have assumed so far that the OpenOffice
project releases, well, OpenOffice. This will still be true, but about
one user in ten millions will want the NetBeans plugin. We can't make
things more complex for the other 99,9% of users due to this.

So for example, one thing we can't do is to partition (now) our
"openoffice" tree into "releases" (for the "real" releases) and
"devtools". If we had known this years ago, it would have made sense
even with the large difference in numbers.

In other words: I would consider
https://dist.apache.org/repos/dist/release/openoffice
to be taken. There will be no "releases" subfolder created in it, to
avoid large management costs for something 99,9% of users won't
use. Either we go for the dirty solution you advocate, where we mix
release numbers and the "devtools" folder (which I don't like, but
this is also not worth a long discussion honestly), or you place the
plugin sources in some existing place.


Should we use something like a devtools subfolder under
release/openoffice so they don't have to be redone for each maintenance
release of AOO or end up with multiples in each AOO release?


Multiple? You will want to look up the distinction between dist and
archive. If you don't find the relevant documentation, just ask and
I'll dig it up from the website.


https://dist.apache.org/repos/dist/release/openoffice/devtools/


I don't know how going for the "dirty" solution will affect scripts.
It will surely result in misaligned trees in dist/ and SourceForge but
this is not particularly problematic. If I recall correctly the
download page options are populated via JS, but in turn that JS is
probably generated (by Marcus?) based on some tree inspection; so this
would need a check too, to ensure the extra "devtools" directory
doesn't get in the way.

On the other hand, the extra "devtools" folder will be ugly, but it
will provide a container for all releases that are not related to our
"main" product.

We could at least agree that http://www.openoffice.org/download/ won't
change at all with the plugin release, right?

Regards,
Andrea.



Andrea,

I hope you don't take my suggestion for disagreement.

I was not the one who pushed for these to be official releases. I am
just trying to make sure they don't confuse or interfere.


and that's great. So, thanks for asking these things. This shows us that 
you care about other things that maybe could be influenced by your work.


Marcus


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



Re: procedure for going from RC to release

2016-04-03 Thread Marcus

Am 04/03/2016 09:42 PM, schrieb Andrea Pescetti:

Carl Marcum wrote:

I was looking at how some other projects handled "extras" things like
this.


Other projects designed their trees in a different way.


I found Maven uses sub-folders under release/maven for plugins,
plugin-tools, etc, that don't go into their main release folder. [1].


Well, here the issue is: we have assumed so far that the OpenOffice
project releases, well, OpenOffice. This will still be true, but about
one user in ten millions will want the NetBeans plugin. We can't make
things more complex for the other 99,9% of users due to this.

So for example, one thing we can't do is to partition (now) our
"openoffice" tree into "releases" (for the "real" releases) and
"devtools". If we had known this years ago, it would have made sense
even with the large difference in numbers.

In other words: I would consider
https://dist.apache.org/repos/dist/release/openoffice
to be taken. There will be no "releases" subfolder created in it, to
avoid large management costs for something 99,9% of users won't use.
Either we go for the dirty solution you advocate, where we mix release
numbers and the "devtools" folder (which I don't like, but this is also
not worth a long discussion honestly), or you place the plugin sources
in some existing place.


Should we use something like a devtools subfolder under
release/openoffice so they don't have to be redone for each maintenance
release of AOO or end up with multiples in each AOO release?


Multiple? You will want to look up the distinction between dist and
archive. If you don't find the relevant documentation, just ask and I'll
dig it up from the website.


https://dist.apache.org/repos/dist/release/openoffice/devtools/


I don't know how going for the "dirty" solution will affect scripts. It
will surely result in misaligned trees in dist/ and SourceForge but this
is not particularly problematic. If I recall correctly the download page
options are populated via JS, but in turn that JS is probably generated
(by Marcus?) based on some tree inspection; so this would need a check
too, to ensure the extra "devtools" directory doesn't get in the way.

On the other hand, the extra "devtools" folder will be ugly, but it will
provide a container for all releases that are not related to our "main"
product.

We could at least agree that http://www.openoffice.org/download/ won't
change at all with the plugin release, right?


of course. As you wrote correctly 99% of our users will not use the 
plugin. And the remaining 1% are no users but devs. And these people 
will use it directly from Netbeans anyway. ;-)


So, I would see releasing the plugin as a part of the open source 
promise: Everybody can have a look into the source code to see what is 
going on - if they like to do it.


Sure, I can implement also this pckage into the JS download scriping and 
provide something on the download page. However, I really doubt that it 
is worth the effort. ;-)


OK seriously, Carl:
- You can do whatever you see fit to release the source package 
regarding filenames, directory structure or where to put it in the tree 
on SourceForge. It will not influence the other AOO download behavior.
Adding it in the "source/" dir along with the other files is OK. Or 
create a new "devtools/" dir.


- When you have some documentation ready or just in mind, don't forget 
to mention this source package incl. a link. Then we can proof that it 
is available as open source.


- As far as I've understood, the important part is the binary at 
Netbeans.org, right? Then we should keep the effort on openoffice.org as 
low as possible as it is just for 1%.


- And, finally, when we see that something was done wrong. OK, then 
let's fix it at the lastest with the next plugin release.


My 2 ct.

Marcus

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



Re: procedure for going from RC to release

2016-04-03 Thread Carl Marcum

On 04/03/2016 04:25 PM, Andrea Pescetti wrote:

Carl Marcum wrote:

I hope you don't take my suggestion for disagreement.


Of course not. Let's simply find together the right way to publish 
this source package in the tree. As I wrote, I am OK with adding 
devtools/ provided this doesn't break the JS generation for download 
page. I see no other significant drawbacks.


Regards,
  Andrea.



Hopefully someone can determine if this will or not.

I have a few different tools I would like to release and don't want to 
dilute the main release folder if it's not necessary.


If there is a problem with this devtools sub-folder or I don't have 
confirmation that it will not be,  I will do as you suggested.


Thanks for your help,
Carl

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



Re: procedure for going from RC to release

2016-04-03 Thread Andrea Pescetti

Carl Marcum wrote:

I hope you don't take my suggestion for disagreement.


Of course not. Let's simply find together the right way to publish this 
source package in the tree. As I wrote, I am OK with adding devtools/ 
provided this doesn't break the JS generation for download page. I see 
no other significant drawbacks.


Regards,
  Andrea.

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



Re: procedure for going from RC to release

2016-04-03 Thread Carl Marcum

On 04/03/2016 03:42 PM, Andrea Pescetti wrote:

Carl Marcum wrote:
I was looking at how some other projects handled "extras" things like 
this.


Other projects designed their trees in a different way.


I found Maven uses sub-folders under release/maven for plugins,
plugin-tools, etc, that don't go into their main release folder. [1].


Well, here the issue is: we have assumed so far that the OpenOffice 
project releases, well, OpenOffice. This will still be true, but about 
one user in ten millions will want the NetBeans plugin. We can't make 
things more complex for the other 99,9% of users due to this.


So for example, one thing we can't do is to partition (now) our 
"openoffice" tree into "releases" (for the "real" releases) and 
"devtools". If we had known this years ago, it would have made sense 
even with the large difference in numbers.


In other words: I would consider
https://dist.apache.org/repos/dist/release/openoffice
to be taken. There will be no "releases" subfolder created in it, to 
avoid large management costs for something 99,9% of users won't 
use. Either we go for the dirty solution you advocate, where we mix 
release numbers and the "devtools" folder (which I don't like, but 
this is also not worth a long discussion honestly), or you place the 
plugin sources in some existing place.



Should we use something like a devtools subfolder under
release/openoffice so they don't have to be redone for each maintenance
release of AOO or end up with multiples in each  AOO release?


Multiple? You will want to look up the distinction between dist and 
archive. If you don't find the relevant documentation, just ask and 
I'll dig it up from the website.



https://dist.apache.org/repos/dist/release/openoffice/devtools/


I don't know how going for the "dirty" solution will affect scripts. 
It will surely result in misaligned trees in dist/ and SourceForge but 
this is not particularly problematic. If I recall correctly the 
download page options are populated via JS, but in turn that JS is 
probably generated (by Marcus?) based on some tree inspection; so this 
would need a check too, to ensure the extra "devtools" directory 
doesn't get in the way.


On the other hand, the extra "devtools" folder will be ugly, but it 
will provide a container for all releases that are not related to our 
"main" product.


We could at least agree that http://www.openoffice.org/download/ won't 
change at all with the plugin release, right?


Regards,
  Andrea.



Andrea,

I hope you don't take my suggestion for disagreement.

I was not the one who pushed for these to be official releases. I am 
just trying to make sure they don't confuse or interfere.


Best regards,
Carl

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



Re: procedure for going from RC to release

2016-04-03 Thread Andrea Pescetti

Carl Marcum wrote:

I was looking at how some other projects handled "extras" things like this.


Other projects designed their trees in a different way.


I found Maven uses sub-folders under release/maven for plugins,
plugin-tools, etc, that don't go into their main release folder. [1].


Well, here the issue is: we have assumed so far that the OpenOffice 
project releases, well, OpenOffice. This will still be true, but about 
one user in ten millions will want the NetBeans plugin. We can't make 
things more complex for the other 99,9% of users due to this.


So for example, one thing we can't do is to partition (now) our 
"openoffice" tree into "releases" (for the "real" releases) and 
"devtools". If we had known this years ago, it would have made sense 
even with the large difference in numbers.


In other words: I would consider
https://dist.apache.org/repos/dist/release/openoffice
to be taken. There will be no "releases" subfolder created in it, to 
avoid large management costs for something 99,9% of users won't use. 
Either we go for the dirty solution you advocate, where we mix release 
numbers and the "devtools" folder (which I don't like, but this is also 
not worth a long discussion honestly), or you place the plugin sources 
in some existing place.



Should we use something like a devtools subfolder under
release/openoffice so they don't have to be redone for each maintenance
release of AOO or end up with multiples in each  AOO release?


Multiple? You will want to look up the distinction between dist and 
archive. If you don't find the relevant documentation, just ask and I'll 
dig it up from the website.



https://dist.apache.org/repos/dist/release/openoffice/devtools/


I don't know how going for the "dirty" solution will affect scripts. It 
will surely result in misaligned trees in dist/ and SourceForge but this 
is not particularly problematic. If I recall correctly the download page 
options are populated via JS, but in turn that JS is probably generated 
(by Marcus?) based on some tree inspection; so this would need a check 
too, to ensure the extra "devtools" directory doesn't get in the way.


On the other hand, the extra "devtools" folder will be ugly, but it will 
provide a container for all releases that are not related to our "main" 
product.


We could at least agree that http://www.openoffice.org/download/ won't 
change at all with the plugin release, right?


Regards,
  Andrea.

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



Re: procedure for going from RC to release

2016-04-03 Thread Carl Marcum

On 04/03/2016 11:49 AM, Andrea Pescetti wrote:

On 03/04/2016 Marcus wrote:

Am 04/03/2016 03:34 PM, schrieb Carl Marcum:
Are the artifacts and signatures copied to new names or recreated 
and signed?


They are moved, using svn move.


If it's for the NetBeans plugin you can look at the name structure above
for the AOO files. Maybe it's possible to adopt it completely or do some
changes where it makes sense.


For the "real" OpenOffice release there is nothing to discuss. Files 
are uploaded to the staging area and from there to dist.


For this "extra" Netbeans plugin release (in the meantime I have taken 
a look at the sources and I found it is much more complex than what I 
thought, so it's reasonable to attempt a proper release) I suggest 
that we add one source-only file to the existing folders.


Specifically (this is extremely important so please ask again for any 
doubts, or you will break a lot of technical assumptions):


1) You upload the RC (one source file, with hashes/signatures) in a 
new subdirectory of https://dist.apache.org/repos/dist/dev/openoffice/ 
(say, 
https://dist.apache.org/repos/dist/dev/openoffice/netbeans-plugin-412-RC1-r180 
); and you call the file something like 
netbeans-plugin-r180.tar.gz, reflecting the SVN revision it comes 
from.


2) After a successful vote, the one file you placed there (accompanied 
by its hashes/signatures) is moved (using svn move) to dist. The 
target directory to use is this one: 
https://dist.apache.org/repos/dist/release/openoffice/4.1.2/source/ ; 
please do not create anything else, the plugin sources will live in 
the source directory of the matching (or closest in time) OpenOffice 
release.


As discussed, binaries for the Netbeans plugin are not released on the 
ASF infrastructure, so after approval you are free to build and sign 
them according to the rules needed on NetBeans.org; and no copy of 
them will be preserved on dist.


Regards,
  Andrea.



Hi Andrea,

Thanks for the very detailed answer.

I was looking at how some other projects handled "extras" things like this.

I found Maven uses sub-folders under release/maven for plugins, 
plugin-tools, etc, that don't go into their main release folder. [1].

Their plugins are source only because they are distributed via Maven Repos.

Should we use something like a devtools subfolder under 
release/openoffice so they don't have to be redone for each maintenance 
release of AOO or end up with multiples in each  AOO release? Something 
like :


https://dist.apache.org/repos/dist/release/openoffice/devtools/

[1] https://dist.apache.org/repos/dist/release/maven/plugins/

Thanks,
Carl

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



Re: procedure for going from RC to release

2016-04-03 Thread Carl Marcum

On 04/03/2016 11:41 AM, Dennis E. Hamilton wrote:

The RC artifact that is approved as a release is the artifact that is released.

If you check the last RC for AOO 4.1.2 at 
 you'll see that the folder 
has the RC name, tied to the source tree.  In that folder, the files are all 
identified by the release those files are a candidate for, not by the RC.

  - Dennis




Somehow I missed that part.

Thanks,
Carl

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



Re: procedure for going from RC to release

2016-04-03 Thread Andrea Pescetti

On 03/04/2016 Marcus wrote:

Am 04/03/2016 03:34 PM, schrieb Carl Marcum:

Are the artifacts and signatures copied to new names or recreated and signed?


They are moved, using svn move.


If it's for the NetBeans plugin you can look at the name structure above
for the AOO files. Maybe it's possible to adopt it completely or do some
changes where it makes sense.


For the "real" OpenOffice release there is nothing to discuss. Files are 
uploaded to the staging area and from there to dist.


For this "extra" Netbeans plugin release (in the meantime I have taken a 
look at the sources and I found it is much more complex than what I 
thought, so it's reasonable to attempt a proper release) I suggest that 
we add one source-only file to the existing folders.


Specifically (this is extremely important so please ask again for any 
doubts, or you will break a lot of technical assumptions):


1) You upload the RC (one source file, with hashes/signatures) in a new 
subdirectory of https://dist.apache.org/repos/dist/dev/openoffice/ (say, 
https://dist.apache.org/repos/dist/dev/openoffice/netbeans-plugin-412-RC1-r180 
); and you call the file something like netbeans-plugin-r180.tar.gz, 
reflecting the SVN revision it comes from.


2) After a successful vote, the one file you placed there (accompanied 
by its hashes/signatures) is moved (using svn move) to dist. The target 
directory to use is this one: 
https://dist.apache.org/repos/dist/release/openoffice/4.1.2/source/ ; 
please do not create anything else, the plugin sources will live in the 
source directory of the matching (or closest in time) OpenOffice release.


As discussed, binaries for the Netbeans plugin are not released on the 
ASF infrastructure, so after approval you are free to build and sign 
them according to the rules needed on NetBeans.org; and no copy of them 
will be preserved on dist.


Regards,
  Andrea.

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



RE: procedure for going from RC to release

2016-04-03 Thread Dennis E. Hamilton
The RC artifact that is approved as a release is the artifact that is released. 
 

If you check the last RC for AOO 4.1.2 at 
<https://dist.apache.org/repos/dist/dev/openoffice/> you'll see that the folder 
has the RC name, tied to the source tree.  In that folder, the files are all 
identified by the release those files are a candidate for, not by the RC.  

 - Dennis



> -Original Message-
> From: Carl Marcum [mailto:cmar...@apache.org]
> Sent: Sunday, April 3, 2016 06:35
> To: dev@openoffice.apache.org
> Subject: procedure for going from RC to release
> 
> I'm looking for the procedure for how the approved RC files are
> released.
> 
> Are the artifacts and signatures copied to new names or recreated and
> signed?
> 
> I know where they go but not how the names are changed.
> 
> Thanks,
> Carl
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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



Re: procedure for going from RC to release

2016-04-03 Thread Marcus

Am 04/03/2016 03:34 PM, schrieb Carl Marcum:

I'm looking for the procedure for how the approved RC files are released.


are you looking for the general release process for AOO? Or for the 
Netbeans plugin you are creating?



Are the artifacts and signatures copied to new names or recreated and
signed?


The installation files are not renamed. The RCs have already the 
release-able name structure:


Apache_OpenOffice_.

Example:
Apache_OpenOffice_4.1.2_Linux_x86-64_install-rpm_de.tar.gz

For a complete overview have a look at the storage location at 
SourceForge.net:


https://sourceforge.net/projects/openofficeorg.mirror/files

Example:
https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.2/binaries/de/


I know where they go but not how the names are changed.


If it's for the NetBeans plugin you can look at the name structure above 
for the AOO files. Maybe it's possible to adopt it completely or do some 
changes where it makes sense.


HTH

Marcus

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



procedure for going from RC to release

2016-04-03 Thread Carl Marcum

I'm looking for the procedure for how the approved RC files are released.

Are the artifacts and signatures copied to new names or recreated and 
signed?


I know where they go but not how the names are changed.

Thanks,
Carl

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



Re: Going

2016-01-29 Thread Marcus

Hi Louis,

thats very sad to read. But thats life. Things are coming and they are 
going and you have to juggle them on your schedule plan.


Thanks a lot for your work and dedication in all these many years. I 
hope you will return someday. :-)


Marcus



Am 01/29/2016 12:39 AM, schrieb Louis Suárez-Potts:

I'm stepping down from the AOO PMC after many years. If one includes the decade 
plus I dedicated to Openoffice.org as the community manager and chair of the 
community council, as well as lead and co-lead of many projects, big and small, 
and the five years since on the PMC, it's been 16 years of OpenOffice. A span 
that has been wonderful, exasperating, exhilarating; and now, for me, it's 
becoming a rut. I'm not contributing much at all, and other open source efforts 
and works take up my time and intellectual focus. Some of these will surely 
intersect with OpenOffice and other Apache projects….

I'll remain subscribed to this and other lists, but am leaving the PMC. You can 
always reach me via the usual ways.


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



Re: Going

2016-01-29 Thread Kay Schenk
On Thu, Jan 28, 2016 at 3:39 PM, Louis Suárez-Potts 
wrote:

> Hi All,
> I'm stepping down from the AOO PMC after many years. If one includes the
> decade plus I dedicated to Openoffice.org as the community manager and
> chair of the community council, as well as lead and co-lead of many
> projects, big and small, and the five years since on the PMC, it's been 16
> years of OpenOffice. A span that has been wonderful, exasperating,
> exhilarating; and now, for me, it's becoming a rut. I'm not contributing
> much at all, and other open source efforts and works take up my time and
> intellectual focus. Some of these will surely intersect with OpenOffice and
> other Apache projects….
>
> I'll remain subscribed to this and other lists, but am leaving the PMC.
> You can always reach me via the usual ways.
>
> Cheers,
> Louis
>
>
> ---
>
> Louis Suárez-Potts
> Skype: louisiam
> Twitter: @luispo
> Personal: http://www.luispo.com/
>
>
>
​Thank you for your service to the PMC since OpenOffice moved to the Apache
Software Foundation.​

I'm happy to see that you're still remaining on the "dev" list. ☺



-- 
--
MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
  -- Carl Bard


Re: Going

2016-01-29 Thread Louis Suárez-Potts

> On 29 Jan 16, at 16:28, Dennis E. Hamilton <orc...@apache.org> wrote:
> 
> Louis,
> 
> I am the one to do that.
> 
> I did not know you wanted to drop your AOO committer karma.
> 
> I will take care of both PMC and committer today.
> 

Thanks, Dennis.

louis


> - Dennis
> 
> 
>> -Original Message-
>> From: Louis Suárez-Potts [mailto:lui...@gmail.com]
>> Sent: Friday, January 29, 2016 10:53
>> To: dev@openoffice.apache.org
>> Subject: Re: Going
>> 
>> 
>>> On 29 Jan 16, at 12:31, Kay Schenk <kay.sch...@gmail.com> wrote:
>>> 
>>> I'm happy to see that you're still remaining on the "dev" list. ☺
>> 
>> I might that way help out or at least gripe entertainingly and
>> occasionally voice the desire that users of AOO and LO be better served
>> by not having to figure out which project to back…..
>> 
>> However…
>> 
>> @Dennis (or ?) can you remove committer privileges from my account? I
>> had presumed that announcing my departure from the PMC was sufficient
>> but it may not be. It may also be that I just have to do it myself….?
>> 
>> cheers,
>> Louis
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail


RE: Going

2016-01-29 Thread Dennis E. Hamilton
Louis,

I am the one to do that.  

I did not know you wanted to drop your AOO committer karma.

I will take care of both PMC and committer today.

 - Dennis


> -Original Message-
> From: Louis Suárez-Potts [mailto:lui...@gmail.com]
> Sent: Friday, January 29, 2016 10:53
> To: dev@openoffice.apache.org
> Subject: Re: Going
> 
> 
> > On 29 Jan 16, at 12:31, Kay Schenk <kay.sch...@gmail.com> wrote:
> >
> > I'm happy to see that you're still remaining on the "dev" list. ☺
> 
> I might that way help out or at least gripe entertainingly and
> occasionally voice the desire that users of AOO and LO be better served
> by not having to figure out which project to back…..
> 
> However…
> 
> @Dennis (or ?) can you remove committer privileges from my account? I
> had presumed that announcing my departure from the PMC was sufficient
> but it may not be. It may also be that I just have to do it myself….?
> 
> cheers,
> Louis


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



Re: Going

2016-01-29 Thread Louis Suárez-Potts

> On 29 Jan 16, at 12:31, Kay Schenk  wrote:
> 
> I'm happy to see that you're still remaining on the "dev" list. ☺

I might that way help out or at least gripe entertainingly and occasionally 
voice the desire that users of AOO and LO be better served by not having to 
figure out which project to back…..

However…

@Dennis (or ?) can you remove committer privileges from my account? I had 
presumed that announcing my departure from the PMC was sufficient but it may 
not be. It may also be that I just have to do it myself….?

cheers,
Louis


signature.asc
Description: Message signed with OpenPGP using GPGMail


RE: Going

2016-01-28 Thread Dennis E. Hamilton
+1

Louis, thank you for your continuous and consistent devotion to OpenOffice, 
ODF, and the whole idea of a multi-platform productivity suite that is freely 
available to everyone.

 - Dennis

> -Original Message-
> From: Carl Marcum [mailto:cmar...@apache.org]
> Sent: Thursday, January 28, 2016 16:39
> To: dev@openoffice.apache.org
> Subject: Re: Going
> 
> On 01/28/2016 06:39 PM, Louis Suárez-Potts wrote:
> > Hi All,
> > I'm stepping down from the AOO PMC after many years. If one includes
> the decade plus I dedicated to Openoffice.org as the community manager
> and chair of the community council, as well as lead and co-lead of many
> projects, big and small, and the five years since on the PMC, it's been
> 16 years of OpenOffice. A span that has been wonderful, exasperating,
> exhilarating; and now, for me, it's becoming a rut. I'm not contributing
> much at all, and other open source efforts and works take up my time and
> intellectual focus. Some of these will surely intersect with OpenOffice
> and other Apache projects….
> >
> > I'll remain subscribed to this and other lists, but am leaving the
> PMC. You can always reach me via the usual ways.
> >
> > Cheers,
> > Louis
> >
> >
> > ---
> >
> > Louis Suárez-Potts
> > Skype: louisiam
> > Twitter: @luispo
> > Personal: http://www.luispo.com/
> >
> 
> Louis,
> 
> Thank you for all of your contributions.
> 
> Good luck on all your endeavors.
> 
> Best regards,
> Carl
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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



Re: Going

2016-01-28 Thread Carl Marcum

On 01/28/2016 06:39 PM, Louis Suárez-Potts wrote:

Hi All,
I'm stepping down from the AOO PMC after many years. If one includes the decade 
plus I dedicated to Openoffice.org as the community manager and chair of the 
community council, as well as lead and co-lead of many projects, big and small, 
and the five years since on the PMC, it's been 16 years of OpenOffice. A span 
that has been wonderful, exasperating, exhilarating; and now, for me, it's 
becoming a rut. I'm not contributing much at all, and other open source efforts 
and works take up my time and intellectual focus. Some of these will surely 
intersect with OpenOffice and other Apache projects….

I'll remain subscribed to this and other lists, but am leaving the PMC. You can 
always reach me via the usual ways.

Cheers,
Louis


---

Louis Suárez-Potts
Skype: louisiam
Twitter: @luispo
Personal: http://www.luispo.com/



Louis,

Thank you for all of your contributions.

Good luck on all your endeavors.

Best regards,
Carl



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



Going

2016-01-28 Thread Louis Suárez-Potts
Hi All,
I'm stepping down from the AOO PMC after many years. If one includes the decade 
plus I dedicated to Openoffice.org as the community manager and chair of the 
community council, as well as lead and co-lead of many projects, big and small, 
and the five years since on the PMC, it's been 16 years of OpenOffice. A span 
that has been wonderful, exasperating, exhilarating; and now, for me, it's 
becoming a rut. I'm not contributing much at all, and other open source efforts 
and works take up my time and intellectual focus. Some of these will surely 
intersect with OpenOffice and other Apache projects….

I'll remain subscribed to this and other lists, but am leaving the PMC. You can 
always reach me via the usual ways.

Cheers,
Louis


---

Louis Suárez-Potts
Skype: louisiam
Twitter: @luispo
Personal: http://www.luispo.com/














signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Facebook Fanpage going direction 10000 Fans

2013-11-04 Thread Rob Weir
On Fri, Nov 1, 2013 at 4:13 PM, Raphael Bircher r.birc...@gmx.ch wrote:
 Hi all

 The Apache OpenOffice Facebook Fanpage going direction 10 k Fans. We hav at
 the Moment 9981 Fans. Just for the Record


We now have 10,031 Facebook Fans.This is good for a Facebook page
that only started in May 2012.

For comparison we have 7,625 on Google + and 2,057 on Twitter.

We have 10,243 subscribers to our announcement mailing list.   So it
is possible that soon we will be able to reach more users via Facebook
than through our announcement list.

-Rob

 Greetings Raphael

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


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



Re: Facebook Fanpage going direction 10000 Fans

2013-11-04 Thread Jürgen Schmidt
On 11/4/13 4:12 PM, Rob Weir wrote:
 On Fri, Nov 1, 2013 at 4:13 PM, Raphael Bircher r.birc...@gmx.ch wrote:
 Hi all

 The Apache OpenOffice Facebook Fanpage going direction 10 k Fans. We hav at
 the Moment 9981 Fans. Just for the Record

 
 We now have 10,031 Facebook Fans.This is good for a Facebook page
 that only started in May 2012.
 
 For comparison we have 7,625 on Google + and 2,057 on Twitter.
 
 We have 10,243 subscribers to our announcement mailing list.   So it
 is possible that soon we will be able to reach more users via Facebook
 than through our announcement list.

we should take this into account or start thinking how we can use it
more effective.

Maybe tips of the day or week ...

Juergen

 
 -Rob
 
 Greetings Raphael

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

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


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



Facebook Fanpage going direction 10000 Fans

2013-11-01 Thread Raphael Bircher

Hi all

The Apache OpenOffice Facebook Fanpage going direction 10 k Fans. We hav 
at the Moment 9981 Fans. Just for the Record


Greetings Raphael

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



Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread jan iversen
I am happy for the help, Clayton has already giving me lot of information,
instead of me having to dig it out. It is also securing to have a helping
hand in the background who know our wiki very well.

Is there a gentle way, to make Infra do the last bit, so I can get access,
as far as I can see it is 2 simple things:
- Copy my ssh public key to the wiki server
- Provide the mysql root password

I am a bit afraid of this long US weekend, and hope we do not have to wait
until next week.

Jan.

On 23 November 2012 09:00, C smau...@gmail.com wrote:

 On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti pesce...@apache.org
 wrote:
  Thanks Clayton, you probably know the inner details of our Mediawiki
  configuration better than most people here, so it is great that you are
  going to coordinate with Jan to neutralize this attack.


 Jan will be leading the defense.  I'll be hanging around more in the
 background trying to explain why things are wonky with historical
 configuration :-)

 The Spam problem can definitely be delt with... just takes a bit of
 time to sort things out, do a few upgrades and a few configuration
 tweaks.

 Meanwhile anyone with current Wiki Admin rights is welcome to scan the
 Recent changes on the Wiki once in a while and:
  - Delete Spam pages (created 1 page every 2 minutes on average)
  - Block the spam accounts (I would suggest that you do not block IP
 address, a check box on the block page, because you risk blocking
 legit users on dynamic IPs)


 Clayton



Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread TJ Frazier

On 11/23/2012 04:20, jan iversen wrote:

I am happy for the help, Clayton has already giving me lot of information,
instead of me having to dig it out. It is also securing to have a helping
hand in the background who know our wiki very well.

Is there a gentle way, to make Infra do the last bit, so I can get access,
as far as I can see it is 2 simple things:
- Copy my ssh public key to the wiki server
- Provide the mysql root password

I am a bit afraid of this long US weekend, and hope we do not have to wait
until next week.

Jan.


Report from the trenches: the spam is getting no worse, but no better 
either. The wonderful crew of volunteers (I play only a small part) is 
getting it all. Max spam page lifetime is about an hour; typical is only 
a few minutes. We may be humans fighting bots, but we're winning — or at 
least not losing. (John Henry said to the captain ...) I also fear the 
long weekend.


The urgent items I see, first = most important:
1) invitation only fix to LocalSettings.php. This turns off the faucet.
2) SQL delete of all unused accounts (no contributions in any space). 
This eliminates the spammers' backlog of new accounts, so we sysops 
don't have to block them one at a time. This will hit a lot of old 
accounts, too. Good; that's overdue. It is possible that a few 
legitimate accounts could be hit, but contributors normally go right in 
and fix something, and/or create their user pages, so those accounts 
should be exempt.


Other items can be dealt with at leisure:
3) Deleting all blocked accounts, the blocks themselves, and any 
associated deleted pages. This is a trash clean-up. It removes any 
backscatter left over from the anti-spam effort, and recovers a minor 
amount of space.

4) Upgrades, extensions, better spam prevention, c.

/tj/



On 23 November 2012 09:00, C smau...@gmail.com wrote:


On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti pesce...@apache.org
wrote:

Thanks Clayton, you probably know the inner details of our Mediawiki
configuration better than most people here, so it is great that you are
going to coordinate with Jan to neutralize this attack.



Jan will be leading the defense.  I'll be hanging around more in the
background trying to explain why things are wonky with historical
configuration :-)

The Spam problem can definitely be delt with... just takes a bit of
time to sort things out, do a few upgrades and a few configuration
tweaks.

Meanwhile anyone with current Wiki Admin rights is welcome to scan the
Recent changes on the Wiki once in a while and:
  - Delete Spam pages (created 1 page every 2 minutes on average)
  - Block the spam accounts (I would suggest that you do not block IP
address, a check box on the block page, because you risk blocking
legit users on dynamic IPs)


Clayton








Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread jan iversen
A big thank to those fighting in the trenches !!!

I am still waiting for infra, but now I am available, so the minute I get
the mail I will be on to it, and change to invite only.

The point list of tj will be my work order. But I hope that someone could
give infra a polite hint, that we really need this closed, infra must
install my ssh public key, and give the mysql root password.

I will open a new thread later, with wiki maintenance, so you all can
follow what is planned to happen (and when it happens).

Clayton pointed me to the maintenance page which contains loads of
valuable information.

jan


On 23 November 2012 11:47, Rory O'Farrell ofarr...@iol.ie wrote:

 On Fri, 23 Nov 2012 05:22:29 -0500
 TJ Frazier tjfraz...@cfl.rr.com wrote:

  On 11/23/2012 04:20, jan iversen wrote:
   I am happy for the help, Clayton has already giving me lot of
 information,
   instead of me having to dig it out. It is also securing to have a
 helping
   hand in the background who know our wiki very well.
  
   Is there a gentle way, to make Infra do the last bit, so I can get
 access,
   as far as I can see it is 2 simple things:
   - Copy my ssh public key to the wiki server
   - Provide the mysql root password
  
   I am a bit afraid of this long US weekend, and hope we do not have to
 wait
   until next week.
  
   Jan.
 
  Report from the trenches: the spam is getting no worse, but no better
  either. The wonderful crew of volunteers (I play only a small part) is
  getting it all. Max spam page lifetime is about an hour; typical is only
  a few minutes. We may be humans fighting bots, but we're winning — or at
  least not losing. (John Henry said to the captain ...) I also fear the
  long weekend.
 
  The urgent items I see, first = most important:
  1) invitation only fix to LocalSettings.php. This turns off the faucet.
  2) SQL delete of all unused accounts (no contributions in any space).
  This eliminates the spammers' backlog of new accounts, so we sysops
  don't have to block them one at a time. This will hit a lot of old
  accounts, too. Good; that's overdue. It is possible that a few
  legitimate accounts could be hit, but contributors normally go right in
  and fix something, and/or create their user pages, so those accounts
  should be exempt.
 
  Other items can be dealt with at leisure:
  3) Deleting all blocked accounts, the blocks themselves, and any
  associated deleted pages. This is a trash clean-up. It removes any
  backscatter left over from the anti-spam effort, and recovers a minor
  amount of space.
  4) Upgrades, extensions, better spam prevention, c.
 
  /tj/
 
  
   On 23 November 2012 09:00, C smau...@gmail.com wrote:
  
   On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti pesce...@apache.org
 
   wrote:
   Thanks Clayton, you probably know the inner details of our Mediawiki
   configuration better than most people here, so it is great that you
 are
   going to coordinate with Jan to neutralize this attack.
  
  
   Jan will be leading the defense.  I'll be hanging around more in the
   background trying to explain why things are wonky with historical
   configuration :-)
  
   The Spam problem can definitely be delt with... just takes a bit of
   time to sort things out, do a few upgrades and a few configuration
   tweaks.
  
   Meanwhile anyone with current Wiki Admin rights is welcome to scan the
   Recent changes on the Wiki once in a while and:
 - Delete Spam pages (created 1 page every 2 minutes on average)
 - Block the spam accounts (I would suggest that you do not block IP
   address, a check box on the block page, because you risk blocking
   legit users on dynamic IPs)
  
  
   Clayton
  
  
 
 
 

 I suggest locking the page for maintenance for the long w/e.

 --
 Rory O'Farrell ofarr...@iol.ie



Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread Oliver-Rainer Wittmann

Hi,

On 23.11.2012 13:47, jan iversen wrote:

A big thank to those fighting in the trenches !!!

I am still waiting for infra, but now I am available, so the minute I get
the mail I will be on to it, and change to invite only.

The point list of tj will be my work order. But I hope that someone could
give infra a polite hint, that we really need this closed, infra must
install my ssh public key, and give the mysql root password.



You can reach ASF infra on irc://freenode/asfinfra

I am on this chat - may be I can pass your requests to them.
command infrabot: beer helps a lot in this chat with ASF infra ;-)

Best regards, Oliver.


I will open a new thread later, with wiki maintenance, so you all can
follow what is planned to happen (and when it happens).

Clayton pointed me to the maintenance page which contains loads of
valuable information.

jan


On 23 November 2012 11:47, Rory O'Farrell ofarr...@iol.ie wrote:


On Fri, 23 Nov 2012 05:22:29 -0500
TJ Frazier tjfraz...@cfl.rr.com wrote:


On 11/23/2012 04:20, jan iversen wrote:

I am happy for the help, Clayton has already giving me lot of

information,

instead of me having to dig it out. It is also securing to have a

helping

hand in the background who know our wiki very well.

Is there a gentle way, to make Infra do the last bit, so I can get

access,

as far as I can see it is 2 simple things:
- Copy my ssh public key to the wiki server
- Provide the mysql root password

I am a bit afraid of this long US weekend, and hope we do not have to

wait

until next week.

Jan.


Report from the trenches: the spam is getting no worse, but no better
either. The wonderful crew of volunteers (I play only a small part) is
getting it all. Max spam page lifetime is about an hour; typical is only
a few minutes. We may be humans fighting bots, but we're winning — or at
least not losing. (John Henry said to the captain ...) I also fear the
long weekend.

The urgent items I see, first = most important:
1) invitation only fix to LocalSettings.php. This turns off the faucet.
2) SQL delete of all unused accounts (no contributions in any space).
This eliminates the spammers' backlog of new accounts, so we sysops
don't have to block them one at a time. This will hit a lot of old
accounts, too. Good; that's overdue. It is possible that a few
legitimate accounts could be hit, but contributors normally go right in
and fix something, and/or create their user pages, so those accounts
should be exempt.

Other items can be dealt with at leisure:
3) Deleting all blocked accounts, the blocks themselves, and any
associated deleted pages. This is a trash clean-up. It removes any
backscatter left over from the anti-spam effort, and recovers a minor
amount of space.
4) Upgrades, extensions, better spam prevention, c.

/tj/



On 23 November 2012 09:00, C smau...@gmail.com wrote:


On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti pesce...@apache.org



wrote:

Thanks Clayton, you probably know the inner details of our Mediawiki
configuration better than most people here, so it is great that you

are

going to coordinate with Jan to neutralize this attack.



Jan will be leading the defense.  I'll be hanging around more in the
background trying to explain why things are wonky with historical
configuration :-)

The Spam problem can definitely be delt with... just takes a bit of
time to sort things out, do a few upgrades and a few configuration
tweaks.

Meanwhile anyone with current Wiki Admin rights is welcome to scan the
Recent changes on the Wiki once in a while and:
   - Delete Spam pages (created 1 page every 2 minutes on average)
   - Block the spam accounts (I would suggest that you do not block IP
address, a check box on the block page, because you risk blocking
legit users on dynamic IPs)


Clayton









I suggest locking the page for maintenance for the long w/e.

--
Rory O'Farrell ofarr...@iol.ie





Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread jan iversen
THANKSwould it not have been nice, if it was noted in the ticket...

I am already looking at opie...so now I only need the mysql root password.

Jan

On 23 November 2012 14:05, Oliver-Rainer Wittmann orwittm...@googlemail.com
 wrote:

 Hi,


 On 23.11.2012 14:01, Oliver-Rainer Wittmann wrote:

 Hi,

 On 23.11.2012 13:47, jan iversen wrote:

 A big thank to those fighting in the trenches !!!

 I am still waiting for infra, but now I am available, so the minute I get
 the mail I will be on to it, and change to invite only.

 The point list of tj will be my work order. But I hope that someone could
 give infra a polite hint, that we really need this closed, infra must
 install my ssh public key, and give the mysql root password.


 You can reach ASF infra on irc://freenode/asfinfra

 I am on this chat - may be I can pass your requests to them.
 command infrabot: beer helps a lot in this chat with ASF infra ;-)


 infra people just told me on irc the following:
 orw: if you see jani tell him he has access and can he please set up opie
 as per.
 orw: Go and have a look at http://s.apache.org/opie to learn how to
 setup OPIE

 Best regards, Oliver.


  Best regards, Oliver.

  I will open a new thread later, with wiki maintenance, so you all can
 follow what is planned to happen (and when it happens).

 Clayton pointed me to the maintenance page which contains loads of
 valuable information.

 jan


 On 23 November 2012 11:47, Rory O'Farrell ofarr...@iol.ie wrote:

  On Fri, 23 Nov 2012 05:22:29 -0500
 TJ Frazier tjfraz...@cfl.rr.com wrote:

  On 11/23/2012 04:20, jan iversen wrote:

 I am happy for the help, Clayton has already giving me lot of

 information,

 instead of me having to dig it out. It is also securing to have a

 helping

 hand in the background who know our wiki very well.

 Is there a gentle way, to make Infra do the last bit, so I can get

 access,

 as far as I can see it is 2 simple things:
 - Copy my ssh public key to the wiki server
 - Provide the mysql root password

 I am a bit afraid of this long US weekend, and hope we do not have to

 wait

 until next week.

 Jan.


 Report from the trenches: the spam is getting no worse, but no better
 either. The wonderful crew of volunteers (I play only a small part) is
 getting it all. Max spam page lifetime is about an hour; typical is
 only
 a few minutes. We may be humans fighting bots, but we're winning — or
 at
 least not losing. (John Henry said to the captain ...) I also fear
 the
 long weekend.

 The urgent items I see, first = most important:
 1) invitation only fix to LocalSettings.php. This turns off the
 faucet.
 2) SQL delete of all unused accounts (no contributions in any space).
 This eliminates the spammers' backlog of new accounts, so we sysops
 don't have to block them one at a time. This will hit a lot of old
 accounts, too. Good; that's overdue. It is possible that a few
 legitimate accounts could be hit, but contributors normally go right in
 and fix something, and/or create their user pages, so those accounts
 should be exempt.

 Other items can be dealt with at leisure:
 3) Deleting all blocked accounts, the blocks themselves, and any
 associated deleted pages. This is a trash clean-up. It removes any
 backscatter left over from the anti-spam effort, and recovers a minor
 amount of space.
 4) Upgrades, extensions, better spam prevention, c.

 /tj/


 On 23 November 2012 09:00, C smau...@gmail.com wrote:

  On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti 
 pesce...@apache.org


  wrote:

 Thanks Clayton, you probably know the inner details of our Mediawiki
 configuration better than most people here, so it is great that you

 are

 going to coordinate with Jan to neutralize this attack.



 Jan will be leading the defense.  I'll be hanging around more in the
 background trying to explain why things are wonky with historical
 configuration :-)

 The Spam problem can definitely be delt with... just takes a bit of
 time to sort things out, do a few upgrades and a few configuration
 tweaks.

 Meanwhile anyone with current Wiki Admin rights is welcome to scan
 the
 Recent changes on the Wiki once in a while and:
- Delete Spam pages (created 1 page every 2 minutes on average)
- Block the spam accounts (I would suggest that you do not block
 IP
 address, a check box on the block page, because you risk blocking
 legit users on dynamic IPs)


 Clayton




Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread Oliver-Rainer Wittmann

Hi,

On 23.11.2012 14:08, jan iversen wrote:

THANKSwould it not have been nice, if it was noted in the ticket...

I am already looking at opie...so now I only need the mysql root password.



infra people told me on irc that it is needed that you setup opie and that you 
should talk directly to them (http://webchat.freenode.net)


Best regards, Oliver.


Jan

On 23 November 2012 14:05, Oliver-Rainer Wittmann orwittm...@googlemail.com

wrote:



Hi,


On 23.11.2012 14:01, Oliver-Rainer Wittmann wrote:


Hi,

On 23.11.2012 13:47, jan iversen wrote:


A big thank to those fighting in the trenches !!!

I am still waiting for infra, but now I am available, so the minute I get
the mail I will be on to it, and change to invite only.

The point list of tj will be my work order. But I hope that someone could
give infra a polite hint, that we really need this closed, infra must
install my ssh public key, and give the mysql root password.



You can reach ASF infra on irc://freenode/asfinfra

I am on this chat - may be I can pass your requests to them.
command infrabot: beer helps a lot in this chat with ASF infra ;-)



infra people just told me on irc the following:
orw: if you see jani tell him he has access and can he please set up opie
as per.
orw: Go and have a look at http://s.apache.org/opie to learn how to
setup OPIE

Best regards, Oliver.


  Best regards, Oliver.


  I will open a new thread later, with wiki maintenance, so you all can

follow what is planned to happen (and when it happens).

Clayton pointed me to the maintenance page which contains loads of
valuable information.

jan


On 23 November 2012 11:47, Rory O'Farrell ofarr...@iol.ie wrote:

  On Fri, 23 Nov 2012 05:22:29 -0500

TJ Frazier tjfraz...@cfl.rr.com wrote:

  On 11/23/2012 04:20, jan iversen wrote:



I am happy for the help, Clayton has already giving me lot of


information,



instead of me having to dig it out. It is also securing to have a



helping



hand in the background who know our wiki very well.


Is there a gentle way, to make Infra do the last bit, so I can get


access,



as far as I can see it is 2 simple things:

- Copy my ssh public key to the wiki server
- Provide the mysql root password

I am a bit afraid of this long US weekend, and hope we do not have to


wait



until next week.


Jan.



Report from the trenches: the spam is getting no worse, but no better
either. The wonderful crew of volunteers (I play only a small part) is
getting it all. Max spam page lifetime is about an hour; typical is
only
a few minutes. We may be humans fighting bots, but we're winning — or
at
least not losing. (John Henry said to the captain ...) I also fear
the
long weekend.

The urgent items I see, first = most important:
1) invitation only fix to LocalSettings.php. This turns off the
faucet.
2) SQL delete of all unused accounts (no contributions in any space).
This eliminates the spammers' backlog of new accounts, so we sysops
don't have to block them one at a time. This will hit a lot of old
accounts, too. Good; that's overdue. It is possible that a few
legitimate accounts could be hit, but contributors normally go right in
and fix something, and/or create their user pages, so those accounts
should be exempt.

Other items can be dealt with at leisure:
3) Deleting all blocked accounts, the blocks themselves, and any
associated deleted pages. This is a trash clean-up. It removes any
backscatter left over from the anti-spam effort, and recovers a minor
amount of space.
4) Upgrades, extensions, better spam prevention, c.

/tj/



On 23 November 2012 09:00, C smau...@gmail.com wrote:

  On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti 

pesce...@apache.org




  wrote:



Thanks Clayton, you probably know the inner details of our Mediawiki
configuration better than most people here, so it is great that you


are



going to coordinate with Jan to neutralize this attack.





Jan will be leading the defense.  I'll be hanging around more in the
background trying to explain why things are wonky with historical
configuration :-)

The Spam problem can definitely be delt with... just takes a bit of
time to sort things out, do a few upgrades and a few configuration
tweaks.

Meanwhile anyone with current Wiki Admin rights is welcome to scan
the
Recent changes on the Wiki once in a while and:
- Delete Spam pages (created 1 page every 2 minutes on average)
- Block the spam accounts (I would suggest that you do not block
IP
address, a check box on the block page, because you risk blocking
legit users on dynamic IPs)


Clayton






Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread jan iversen
I am trying, sadly enough I missed orwI still think my problem is
accessing the wiki

orw, is just a user like the rest of us and not infra, but his idea was good

Oliver: thanks for trying to help.

jan

On 23 November 2012 14:26, Oliver-Rainer Wittmann orwittm...@googlemail.com
 wrote:

 Hi,


 On 23.11.2012 14:08, jan iversen wrote:

 THANKSwould it not have been nice, if it was noted in the ticket...

 I am already looking at opie...so now I only need the mysql root password.


 infra people told me on irc that it is needed that you setup opie and that
 you should talk directly to them (http://webchat.freenode.net)

 Best regards, Oliver.


  Jan

 On 23 November 2012 14:05, Oliver-Rainer Wittmann 
 orwittm...@googlemail.com

 wrote:


  Hi,


 On 23.11.2012 14:01, Oliver-Rainer Wittmann wrote:

  Hi,

 On 23.11.2012 13:47, jan iversen wrote:

  A big thank to those fighting in the trenches !!!

 I am still waiting for infra, but now I am available, so the minute I
 get
 the mail I will be on to it, and change to invite only.

 The point list of tj will be my work order. But I hope that someone
 could
 give infra a polite hint, that we really need this closed, infra must
 install my ssh public key, and give the mysql root password.


  You can reach ASF infra on irc://freenode/asfinfra

 I am on this chat - may be I can pass your requests to them.
 command infrabot: beer helps a lot in this chat with ASF infra ;-)


  infra people just told me on irc the following:
 orw: if you see jani tell him he has access and can he please set up
 opie
 as per.
 orw: Go and have a look at http://s.apache.org/opie to learn how to
 setup OPIE

 Best regards, Oliver.


   Best regards, Oliver.


   I will open a new thread later, with wiki maintenance, so you all
 can

 follow what is planned to happen (and when it happens).

 Clayton pointed me to the maintenance page which contains loads of
 valuable information.

 jan


 On 23 November 2012 11:47, Rory O'Farrell ofarr...@iol.ie wrote:

   On Fri, 23 Nov 2012 05:22:29 -0500

 TJ Frazier tjfraz...@cfl.rr.com wrote:

   On 11/23/2012 04:20, jan iversen wrote:


  I am happy for the help, Clayton has already giving me lot of

  information,


  instead of me having to dig it out. It is also securing to have a


  helping


  hand in the background who know our wiki very well.


 Is there a gentle way, to make Infra do the last bit, so I can get

  access,


  as far as I can see it is 2 simple things:

 - Copy my ssh public key to the wiki server
 - Provide the mysql root password

 I am a bit afraid of this long US weekend, and hope we do not have
 to

  wait


  until next week.


 Jan.


 Report from the trenches: the spam is getting no worse, but no better
 either. The wonderful crew of volunteers (I play only a small part)
 is
 getting it all. Max spam page lifetime is about an hour; typical is
 only
 a few minutes. We may be humans fighting bots, but we're winning — or
 at
 least not losing. (John Henry said to the captain ...) I also fear
 the
 long weekend.

 The urgent items I see, first = most important:
 1) invitation only fix to LocalSettings.php. This turns off the
 faucet.
 2) SQL delete of all unused accounts (no contributions in any space).
 This eliminates the spammers' backlog of new accounts, so we sysops
 don't have to block them one at a time. This will hit a lot of old
 accounts, too. Good; that's overdue. It is possible that a few
 legitimate accounts could be hit, but contributors normally go right
 in
 and fix something, and/or create their user pages, so those accounts
 should be exempt.

 Other items can be dealt with at leisure:
 3) Deleting all blocked accounts, the blocks themselves, and any
 associated deleted pages. This is a trash clean-up. It removes any
 backscatter left over from the anti-spam effort, and recovers a minor
 amount of space.
 4) Upgrades, extensions, better spam prevention, c.

 /tj/


  On 23 November 2012 09:00, C smau...@gmail.com wrote:

   On Fri, Nov 23, 2012 at 1:16 AM, Andrea Pescetti 

 pesce...@apache.org


wrote:


  Thanks Clayton, you probably know the inner details of our
 Mediawiki
 configuration better than most people here, so it is great that
 you

  are


  going to coordinate with Jan to neutralize this attack.




 Jan will be leading the defense.  I'll be hanging around more in
 the
 background trying to explain why things are wonky with historical
 configuration :-)

 The Spam problem can definitely be delt with... just takes a bit of
 time to sort things out, do a few upgrades and a few configuration
 tweaks.

 Meanwhile anyone with current Wiki Admin rights is welcome to scan
 the
 Recent changes on the Wiki once in a while and:
 - Delete Spam pages (created 1 page every 2 minutes on average)
 - Block the spam accounts (I would suggest that you do not
 block
 IP
 address, a check box on the block page, because you risk blocking
 legit users on dynamic IPs)


 Clayton






Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-23 Thread jan iversen
 here, so it is great that
  you
 
   are
 
 
   going to coordinate with Jan to neutralize this attack.
 
 
 
 
  Jan will be leading the defense.  I'll be hanging around more in
  the
  background trying to explain why things are wonky with
 historical
  configuration :-)
 
  The Spam problem can definitely be delt with... just takes a
 bit of
  time to sort things out, do a few upgrades and a few
 configuration
  tweaks.
 
  Meanwhile anyone with current Wiki Admin rights is welcome to
 scan
  the
  Recent changes on the Wiki once in a while and:
  - Delete Spam pages (created 1 page every 2 minutes on
 average)
  - Block the spam accounts (I would suggest that you do not
  block
  IP
  address, a check box on the block page, because you risk
 blocking
  legit users on dynamic IPs)
 
 
  Clayton
 
 
 
 
 


 --
 Best regards,
 imacat ^_*' ima...@mail.imacat.idv.tw
 PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

 Woman's Voice News: http://www.wov.idv.tw/
 Tavern IMACAT's http://www.imacat.idv.tw/
 Woman in FOSS in Taiwan http://wofoss.blogspot.com/
 OpenOffice http://www.openoffice.org/
 EducOO/OOo4Kids http://www.openoffice.org/EducOO/OOo4Kids Taiwan
 http://www.educoo.tw/
 Greenfoot Taiwan http://greenfoot.westart.tw/




Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-22 Thread C
On Thu, Nov 22, 2012 at 8:29 PM, Rory O'Farrell wrote:
 Thank, Clayton.  I was wondering if there might be a malicious anti-AOO 
 intent behind the spam, but from what you say it does not seem likely.

It's definitely not anti-OOo vandalism.  Just the usual blog/SEO spam.

Clayton


Re: Wiki spamming is going to get worse if something isn't done soon...

2012-11-22 Thread Andrea Pescetti

On 22/11/2012 C wrote:

TJ pointed me at the Wiki Spam problem.  I can try to lend a hand.


Thanks Clayton, you probably know the inner details of our Mediawiki 
configuration better than most people here, so it is great that you are 
going to coordinate with Jan to neutralize this attack.


Regards,
  Andrea.


Re: How is the conference going in SinSheim?

2012-11-08 Thread Yue Helen
Hi Andrea,

Although not there, read your slides online, it's terrific! A wonderful
presentation, with great summary and vision.

Helen

2012/11/8 Andrea Pescetti pesce...@apache.org

 Kay Schenk wrote:

 Yes! No begrudging their busy-ness from me.  I'm sure we'll hear lots on
 the weekend!


 It's really nice to see that many people eager to know about ApacheCon!

 Thanks to Armin's account we now have a draft blog post covering day 1 at
 https://blogs.apache.org/**preview/OOo/?previewEntry=**
 openoffice_track_at_apachecon_**dayhttps://blogs.apache.org/preview/OOo/?previewEntry=openoffice_track_at_apachecon_day

 which will need to be completed soon with proper embedding of my
 presentation (iframe is apparently blocked, so I'll replace it with an img
 linked to Slideshare and imacat's material).

 Since the content was already reviewed by people here, I'd fast track it
 for publication as soon as we get these last details in place. The link is
 a preview link: please don't share before it's published.

 Feel free to make edits/corrections directly online, it's best for us.

 Regards,
   Andrea.



Re: How is the conference going in SinSheim?

2012-11-08 Thread imacat
On 2012/11/08 07:37, Andrea Pescetti aid:
 On 07/11/2012 Fan Zheng wrote:
 Suggestion:
 We should assign a specified person be responsible to broadcasting the
 status and the progress online, before the next CONF.
 
 I agree, but choose someone who is not a speaker and make sure he has
 access to Roller (and has actually tried to use it) before the
 conference starts. This way we can be sure that communication will be
 efficient.

I'm kind of doing it now, on our Google plus and Facebook.  Although I
started it a little late and only posted the current topic.

 
 Regards,
   Andrea.


-- 
Best regards,
imacat ^_*' ima...@mail.imacat.idv.tw
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

Woman's Voice News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/
Greenfoot Taiwan http://greenfoot.westart.tw/



signature.asc
Description: OpenPGP digital signature


Re: How is the conference going in SinSheim?

2012-11-07 Thread Andrea Pescetti

Kay Schenk wrote:

When you get this ON the blog, let us know so we can highlight it in the
right hand panel.


Blog post now live. It is the report of Day 1. I hope reporting about 
Day 2 and Day 3 will work more smoothly, and since I now have a working 
Roller account (thanks Marcus) I'll take care of Day 2.


You can find Day 1 at
https://blogs.apache.org/OOo/entry/openoffice_track_at_apachecon_day

Regards,
  Andrea.