Re: Experience using WSL2 on Windows

[DurgaPrasad Potnuru]

with wsl we can run multiple linux distributions from windows itself, this
would be interesting and pretty useful in developing apps for multiple
platforms (such as openoffice)

seems wsl is already being considered widely for running linux based apps
from windows   Ex:
https://backstage.io/docs/getting-started/configuration#prerequisites

looking forward to progress on this

On Sat, Jul 8, 2023 at 1:35 PM Matthias Seidel 
wrote:

> Hi Peter,
>
> Am 08.07.23 um 05:41 schrieb Peter Kovacs:
> > [1] https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
>
> Nice find!
>
> I knew about X11, but support for Wayland was new to me.
>
> Maybe I will try it... ;-)
>
> Regards,
>
>Matthias
>
> >
> > Am 22.06.23 um 10:51 schrieb Matthias Seidel:
> >> Hi,
> >>
> >> Am 22.06.23 um 08:14 schrieb DurgaPrasad Potnuru:
> >>> Hi Keith
> >>> Bit curious. WSL2 is command line, how would you be checking the
> >>> desktop
> >>> app on the same?
> >> WSL2 is capable to run graphical Linux applications.
> >>
> >> At least simple ones, like gedit or gtkhash run on my Windows 10. I
> >> would be curious if AOO would even start...
> >
> > according to Microsoft documendtation you can run gimp. see [1]
> >
> > worth a try
> >
> >
> >>
> >> But for real testing I recommend virtual machines with standard Linux
> >> distributions.
> >>
> >> Regards,
> >>
> >> Matthias
> >>
> >>> On Thu, 22 Jun, 2023, 1:35 am Keith N. McKenna,
> >>> 
> >>> wrote:
> >>>
> >>>> I have been considering WSL2 on a Windows 11 system to be able to
> >>>> better
> >>>> contribute to the QA process by having a Linux version of AOO to run
> >>>> Bugzilla entries against as well as my Windows system.
> >>>>
> >>>> If anyone has any experience with WSL I would be interested in hearing
> >>>> about any pros and cons anyone has had with it
> >>>>
> >>>> Regards
> >>>> Keith
> >>>>
> >>>>
> >>>> -
> >>>> 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: Experience using WSL2 on Windows

[DurgaPrasad Potnuru]

Hi Keith
Bit curious. WSL2 is command line, how would you be checking the desktop
app on the same?

On Thu, 22 Jun, 2023, 1:35 am Keith N. McKenna, 
wrote:

> I have been considering WSL2 on a Windows 11 system to be able to better
> contribute to the QA process by having a Linux version of AOO to run
> Bugzilla entries against as well as my Windows system.
>
> If anyone has any experience with WSL I would be interested in hearing
> about any pros and cons anyone has had with it
>
> Regards
> Keith
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: blog migration

[DurgaPrasad Potnuru]

Awesome, will get started on it and will confirm

On Fri, 9 Jun, 2023, 2:08 am Peter Kovacs,  wrote:

> cool! DurgaPrasad Potnuru,
>
>
> All you need is a github account. And a local git installation. I use
> Codium (a variation of Visual Code) as an editor. but you can use others.
>
>
> fork the Project https://github.com/apache/openoffice-project - on the
> page top right you see a button "Fork"
>
> then clone the project to your machine. git clone
>
> switch to the branch missing-pictures and continue editing.
>
>
> lf you want to check the results offline you can follow guide
> https://infra.apache.org/asf-pelican-local.html. (the script will clone
> the site ) But the setup does only work on mac and Linux.
>
> Once done with your work, sync with your fork. On github create a merge
> request back to apache missing-pictures branch. A button should apear
> automaticly, just check for the right branch.
>
>
>
> All the best
>
> Peter
>
>
>
> Am 08.06.23 um 15:25 schrieb DurgaPrasad Potnuru:
> > Hello Peter
> > Happy to pitch in
> >
> > Which aspect can we help with.
> > What are the access needed for the same.
> >
> >
> >
> > On Thu, 8 Jun, 2023, 2:28 pm Peter Kovacs,  wrote:
> >
> >> Okay, that was not smart. For some reason I missed that a lot of
> >> pictures referenced to the blog.
> >>
> >> I have started to fix this on branch
> >> https://openoffice-missing-pictures.staged.apache.org/blogpage.html
> >>
> >> you can preview the results here:
> >> https://openoffice-missing-pictures.staged.apache.org/
> >>
> >>
> >> and I could use some help.
> >>
> >> I save the pictures from:
> >>
> https://web.archive.org/web/20170119032007/https://blogs.apache.org/OOo/
> >> into content/images/blog
> >>
> >> rename to blogname_picturetitle.filetype
> >>
> >> change the link to "../images/blog/blogname_picturetitle.filetype"
> >>
> >>
> >> 2 articles have been fixed. 50 mill downloads and 1 year developer
> >>
> >> If someone wants to help, Please answer here.
> >>
> >> All the best
> >>
> >> Peter
> >>
> >> Am 08.06.23 um 09:03 schrieb Peter Kovacs:
> >>> Ahh yes, I messed up a little. let me check.
> >>>
> >>> Am 07.06.23 um 20:32 schrieb Matthias Seidel:
> >>>> Hi all,
> >>>>
> >>>> Sorry for the confusion, I looked into /blog, not on /blogpage.html.
> >>>>
> >>>> But I think the page does not build...
> >>>>
> >>>> Regards,
> >>>>
> >>>>  Matthias
> >>>>
> >>>> Am 07.06.23 um 20:25 schrieb Matthias Seidel:
> >>>>> Hi All,
> >>>>>
> >>>>> Am 06.06.23 um 19:24 schrieb Marcus:
> >>>>>> Am 02.06.23 um 23:05 schrieb Peter Kovacs:
> >>>>>>> The roller migration can be reviewed at [1].
> >>>>>>>
> >>>>>>> Please, have a look through the page if something broke that I
> >>>>>>> missed. Or Other things we need to look at.
> >>>>>>>
> >>>>>>> All pages where moved into a page sub folder. In folder blogs
> all
> >>>>>>> our blog post can be found.
> >>>>>> that's great news! Thanks a lot for the migration. :-)
> >>>>>>
> >>>>>>> Open Points fron my side:
> >>>>>>>
> >>>>>>> # FAQ - Blog needs to be rewritten
> >>>>>> I don't see a FAQ that needs to be rewritten. However, it's just the
> >>>>>> same step as you would edit another webpage.
> >>>>> Ooops, I just edited a few external links and now the blog looks a
> bit
> >>>>> "different"
> >>>>>
> >>>>> I edited in /blog, should I edit in /blog_entry ?
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>>  Matthias
> >>>>>
> >>>>>>> # figure out how we can automate the Announcement part in General
> >>>>>>> about
> >>>>>> Yes, could be done. But it's no big deal to do it manually. It's
> just
> >>>>>> - copy & paste the old text+links
> >>>&

Re: blog migration

[DurgaPrasad Potnuru]

Hello Peter
Happy to pitch in

Which aspect can we help with.
What are the access needed for the same.



On Thu, 8 Jun, 2023, 2:28 pm Peter Kovacs,  wrote:

> Okay, that was not smart. For some reason I missed that a lot of
> pictures referenced to the blog.
>
> I have started to fix this on branch
> https://openoffice-missing-pictures.staged.apache.org/blogpage.html
>
> you can preview the results here:
> https://openoffice-missing-pictures.staged.apache.org/
>
>
> and I could use some help.
>
> I save the pictures from:
> https://web.archive.org/web/20170119032007/https://blogs.apache.org/OOo/
> into content/images/blog
>
> rename to blogname_picturetitle.filetype
>
> change the link to "../images/blog/blogname_picturetitle.filetype"
>
>
> 2 articles have been fixed. 50 mill downloads and 1 year developer
>
> If someone wants to help, Please answer here.
>
> All the best
>
> Peter
>
> Am 08.06.23 um 09:03 schrieb Peter Kovacs:
> > Ahh yes, I messed up a little. let me check.
> >
> > Am 07.06.23 um 20:32 schrieb Matthias Seidel:
> >> Hi all,
> >>
> >> Sorry for the confusion, I looked into /blog, not on /blogpage.html.
> >>
> >> But I think the page does not build...
> >>
> >> Regards,
> >>
> >> Matthias
> >>
> >> Am 07.06.23 um 20:25 schrieb Matthias Seidel:
> >>> Hi All,
> >>>
> >>> Am 06.06.23 um 19:24 schrieb Marcus:
>  Am 02.06.23 um 23:05 schrieb Peter Kovacs:
> > The roller migration can be reviewed at [1].
> >
> > Please, have a look through the page if something broke that I
> > missed. Or Other things we need to look at.
> >
> >All pages where moved into a page sub folder. In folder blogs all
> > our blog post can be found.
>  that's great news! Thanks a lot for the migration. :-)
> 
> > Open Points fron my side:
> >
> > # FAQ - Blog needs to be rewritten
>  I don't see a FAQ that needs to be rewritten. However, it's just the
>  same step as you would edit another webpage.
> >>> Ooops, I just edited a few external links and now the blog looks a bit
> >>> "different"
> >>>
> >>> I edited in /blog, should I edit in /blog_entry ?
> >>>
> >>> Regards,
> >>>
> >>> Matthias
> >>>
> > # figure out how we can automate the Announcement part in General
> > about
>  Yes, could be done. But it's no big deal to do it manually. It's just
>  - copy & paste the old text+links
>  - exchange a few data
>  - and that's it ;-)
> 
> > # fixate the banner and menu on top without overlap effect
>  I don't see a different behavior when I open / close the Project menu
>  - compared with the other menu items.
> 
>  Another point:
>  The separator line and the "Continue Reading" link are differently
>  positioned for every blog item. It depends how long the blog text is.
>  So, the text length could be fixed. Let's see.
> 
>  Marcus
> 
> 
>  -
>  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] add an unsubscribe/help footer to recruitment ML

[DurgaPrasad Potnuru]

+1

On Sun, Feb 7, 2021 at 9:29 PM Peter Kovacs  wrote:

> For me, too. 'Thanks a lot Carl.
>
> On 07.02.21 16:41, Marcus wrote:
> > Am 07.02.21 um 16:36 schrieb Carl Marcum:
> >> The unsubscribe and help footer has been added to recruitment@ list.
> >
> > ... and it's working for me.
> >
> > Thanks
> >
> > Marcus
> >
> >> On 1/25/21 6:45 PM, Carl Marcum wrote:
> >>> On 1/19/21 12:23 PM, Marcus wrote:
>  Am 19.01.21 um 01:08 schrieb Carl Marcum:
> > On 1/17/21 3:41 PM, Andrea Pescetti wrote:
> >> On 10/01/2021 Peter Kovacs wrote:
> >>> On 10.01.21 23:42, Andrea Pescetti wrote:
>  But we should also be more proactive and remove people when
>  they ask for it on the list: Whimsy https://whimsy.apache.org/
> ...
> >>> The moderators are Patricia, Andrea and Marcus.
> >>
> >> I confirm that indeed I use Whimsy to help people unsubscribe the
> >> recruitment list when their intention is clear and when they are
> >> confused about how to do it. I hope the new footer will help
> >> limit these cases.
> >>
> > So should I go ahead with this if we are renaming the list?
> > I don't to create work for infra if it's not needed.
> 
>  I haven't seen any objection since days, so I would assume that a)
>  renaming the mailing list and b) adding a footer is OK.
> 
>  Please go ahead. :-)
> 
>  Marcus
> 
> >>> I put in a ticket for the footer [1].
> >>>
> >>> The rename I'll let someone else submit.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/INFRA-21343
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> --
> This is the Way! http://www.apache.org/theapacheway/index.html
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: [proposal] going Agile

[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: Organizing testing for 4.2.0

[DurgaPrasad Potnuru]

+1

(willing to work in coordinated test approach, let me know how can I
contribute.. am not familiar with test plans for earlier version, so might
require some (minimal) guidance)

On Tue, Jan 9, 2018 at 4:43 AM, Peter Kovacs  wrote:

> Hi all,
>
> With 4.2.0 in the pipe we need to substential tests.
> Since we have figured in 4.1.4 that we need a more substential testing, I
> wonder if we have volunteers that are willed to work in a more coordinated
> test approach.
>
> My Idea would be to organize a testplan, which tries to cover a good
> amount of features used in the day to day live.
> Then we write testcases, including test documents.
> The goal would be that we can in the end efficiently execute testing,
> maybe involving more people who would like to help out but dont know where
> to start.
>
> What do you think?
>
> Please keep both list in the list for now. I do not know how many read
> both lists. even if QA is pretty silent. (But I know QA people who are not
> on development lists, so I use both.)
>
> All the best
> Peter
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

[CWiki] Account Whitelisting

[DurgaPrasad Potnuru]

Username/email - pvvdurgapra...@gmail.com
Fullname - V V DURGAPRASAD POTNURU