Re: Meeting Minutes : Amanda Open Source Community

2019-03-19 Thread Gene Heskett
On Tuesday 19 March 2019 15:25:55 J Chapman Flack wrote:

> On 3/19/19 2:31 PM, Gene Heskett wrote:
> > Here's what I have ATM.
> > ...
> > amanda-4.0.0alpha.svn.4700.tar.gz
> > ...
> > amanda-4.0.0alpha.svn.5199.tar.gz
>
> Did those come from the SVN repo at https://sourceforge.net/p/amanda ?
> Or is there another I've overlooked?
I believe they did, it was while a Dustin Mitchel was working on it about 
5 years ago now, but the grant $ ran out, and he went elsewhere since he 
was fond of eating and such.

> The one at sourceforge has a latest revision r7719 from 14 Feb 2019.

Does it work?  And whose name is in the release notes?

> The mirror at https://github.com/zmanda/amanda seems to stop at
> git commit b2fd140, which corresponds to svn r7714 about a year
> earlier. Then apparently the updates to git stopped happening.
>
> The later commits I see in sourceforge svn are:
> 7715 (branch 3_5) for filtering arguments to GNU tar
> 7716 (branch 3_5) for security review comments fixes
> 7717 (creates branch 3_5_Debug from 3_5)
> 7718 (branch 3_5_Debug) changes to s3 device
> 7719 (branch 3_5_Debug) adds debug logging for s3
>
> > Start a new github entry as amanda-4-alpha.
>
> Surely the way to go would be to fork the existing github repo
> (for preservation of all existing history and commit IDs) and
> catch it up (via git-svn) to any history in the svn repo that
> isn't mirrored over yet?

However that is done. I am not familiar with those tools.
>
> Or is the 4.0.0alpha stuff coming from some completely different
> repository?

DNK for sure. But for a while, there was a new one about weekly. This was 
in 2012 according to the dates on those, the last time any major work 
was done on it. At the time, the major push was to rewrite it in perl.

What amazes me is that Jean-Louis M. has been quiet, too quiet, as if he 
has been silenced.

> -Chap



Copyright 2018 by Maurice E. HeskettCheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: Meeting Minutes : Amanda Open Source Community

2019-03-19 Thread J Chapman Flack
On 3/19/19 2:31 PM, Gene Heskett wrote:

> Here's what I have ATM.
> ...
> amanda-4.0.0alpha.svn.4700.tar.gz
> ...
> amanda-4.0.0alpha.svn.5199.tar.gz

Did those come from the SVN repo at https://sourceforge.net/p/amanda ?
Or is there another I've overlooked?

The one at sourceforge has a latest revision r7719 from 14 Feb 2019.

The mirror at https://github.com/zmanda/amanda seems to stop at
git commit b2fd140, which corresponds to svn r7714 about a year
earlier. Then apparently the updates to git stopped happening.

The later commits I see in sourceforge svn are:
7715 (branch 3_5) for filtering arguments to GNU tar
7716 (branch 3_5) for security review comments fixes
7717 (creates branch 3_5_Debug from 3_5)
7718 (branch 3_5_Debug) changes to s3 device
7719 (branch 3_5_Debug) adds debug logging for s3

> Start a new github entry as amanda-4-alpha.

Surely the way to go would be to fork the existing github repo
(for preservation of all existing history and commit IDs) and
catch it up (via git-svn) to any history in the svn repo that
isn't mirrored over yet?

Or is the 4.0.0alpha stuff coming from some completely different
repository?

-Chap


Re: Meeting Minutes : Amanda Open Source Community

2019-03-19 Thread Gene Heskett
On Tuesday 19 March 2019 13:18:58 Stefan G. Weichinger wrote:

> Am 17.10.18 um 22:37 schrieb Ashwin Krishna:
> >> So is Jean-Louis still involved or not? Employed by Betsol or ...
> >> ?
> >
> > Jean Louis is not with BETSOL. He is part of the community though.
> > The previous call was to understand the pain points of the community
> > in general for governance and contributions. Based on the feedback
> > from those who attended, we have come up with the action plan as
> > mentioned in the previous mail and we will drive it.
> >
> >> What features do we need, is there a plan to further migrate to
> >> perl code, what are the platforms covered, etc
> >
> > As we have been with Amanda for a very short time, we will gradually
> > get there. Meanwhile, any of the existing members want to take up
> > the initiative to drive this?
>
> Ashwin, or other folks@betsol:
>
> any news here?
>
> This is ~5 months old ... please announce how things will be handled
> in future.
>
> Issues and bug-reports pile at github, the project has stalled
> completely from my point of view.
>
Mine too. Betsol so far has proved themselves to be a bunch of losers 
who despite the promises, have not delivered one word of code in any 
language.

As a user of 20 years, I hate to see a good project wither away from a 
total lack of interest on the part of the owners, so it puzzles me no 
end why they even bought it in the first place.

My original idea was, and still is to fork it.
 
> Maybe you write amanda-4.0 already, who knows?

We already have about 6 months worth of 4.0-alpha, many of which worked, 
I've tested them.  That might be a good starting point for a fork. 

Here's what I have ATM.

root@coyote:/home/amanda# ls -l *.tar.gz
-rw-r--r-- 1 amanda disk 4567086 Jul 31  2014 amanda-3.3.6.tar.gz
-rw-r--r-- 1 amanda disk 4617708 Feb 16  2015 amanda-3.3.7p1.tar.gz
-rw-r--r-- 1 amanda disk 5355137 Mar  3  2017 amanda-3.4.3.tar.gz
-rw-r--r-- 1 amanda disk 5402093 Oct  2 13:31 amanda-3.5.1.tar.gz
-rw-rw-r-- 1 amanda disk 4316872 May  9  2012 amanda-4.0.0alpha.svn.4700.tar.gz
-rw-rw-r-- 1 amanda disk 4322244 May 11  2012 amanda-4.0.0alpha.svn.4719.tar.gz
-rw-rw-r-- 1 amanda disk 4322155 May 12  2012 amanda-4.0.0alpha.svn.4721.tar.gz
-rw-rw-r-- 1 amanda disk 4322245 May 14  2012 amanda-4.0.0alpha.svn.4725.tar.gz
-rw-rw-r-- 1 amanda disk 4323066 May 16  2012 amanda-4.0.0alpha.svn.4731.tar.gz
-rw-rw-r-- 1 amanda disk 4323471 May 24  2012 amanda-4.0.0alpha.svn.4745.tar.gz
-rw-rw-r-- 1 amanda disk 4323552 May 30  2012 amanda-4.0.0alpha.svn.4747.tar.gz
-rw-rw-r-- 1 amanda disk 4323761 Jun  7  2012 amanda-4.0.0alpha.svn.4755.tar.gz
-rw-rw-r-- 1 amanda disk 4324755 Jun 14  2012 amanda-4.0.0alpha.svn.4759.tar.gz
-rw-rw-r-- 1 amanda disk 4325672 Jun 15  2012 amanda-4.0.0alpha.svn.4761.tar.gz
-rw-r--r-- 1 amanda disk 4608589 Jun 23  2013 amanda-4.0.0alpha.svn.5199.tar.gz

AIR 4759 worked, using 3.3.7p1 clients. I do not recall if 4761 or 5199 
did. But there's your src to fork it.

If there is any interest by this group to build it and try it, I'll make 
them visible on my web page. Start a new github entry as amanda-4-alpha.

> Let us know ...

Do they even exist?

> Thanks, regards, Stefan



Copyright 2018 by Maurice E. Heskett
Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: Meeting Minutes : Amanda Open Source Community

2019-03-19 Thread Stefan G. Weichinger
Am 17.10.18 um 22:37 schrieb Ashwin Krishna:
>> So is Jean-Louis still involved or not? Employed by Betsol or ...
>> ?
> 
> Jean Louis is not with BETSOL. He is part of the community though. 
> The previous call was to understand the pain points of the community
> in general for governance and contributions. Based on the feedback
> from those who attended, we have come up with the action plan as
> mentioned in the previous mail and we will drive it.
> 
>> What features do we need, is there a plan to further migrate to
>> perl code, what are the platforms covered, etc
> 
> As we have been with Amanda for a very short time, we will gradually
> get there. Meanwhile, any of the existing members want to take up the
> initiative to drive this?

Ashwin, or other folks@betsol:

any news here?

This is ~5 months old ... please announce how things will be handled in
future.

Issues and bug-reports pile at github, the project has stalled
completely from my point of view.

Maybe you write amanda-4.0 already, who knows?

Let us know ...

Thanks, regards, Stefan


Re: Meeting Minutes : Amanda Open Source Community

2018-12-04 Thread Stefan G. Weichinger
Am 05.12.18 um 04:11 schrieb Uwe Menges:
> On 10/17/18 10:37 PM, Ashwin Krishna wrote:
>> The previous call was to understand the pain points of the community
>> in general for governance and contributions. Based on the feedback
>> from those who attended, we have come up with the action plan as
>> mentioned in the previous mail and we will drive it.
> 
> [BUMP]
> 
> I didn't see a very concrete action plan with responsibilities or dates
> in the previous e-mail.
> 
> I don't know anything about the situation at BETSOL, Zmanda, JLM with
> regards to staffing and funding for the amanda / Zmanda development (or
> in general). Or how the development process used to be, besides what can
> be seen on github.
> 
> So here's my 2ct.
> 
> As the meeting minutes state and others already pointed out we should
> probably use github with wiki. So someone with access rights should tick
> [x] Wikis on github's Settings page and/or enable Pages. AFAICS there
> are two people, martineau and NingZhangWisc according to
> .
> 
> ASAP you (or we?) should find someone to enable small PR merges so eg.
> Dustins fix PR#92 and others can get into a minor version bump later.
> 
> There probably needs to be a software architect that decides directions
> for heavier things like Chap's PR#78. Is there one? Are there (paid?)
> people working on github issues?
> 
> The suggestions from Dustin were also good and should find their way in
> some kind of roadmap (which could be a simple .md on github).
> 
> Some eg. monthly information for the community what's happening behind
> the scenes would be nice.

+2ct from me




Re: Meeting Minutes : Amanda Open Source Community

2018-12-04 Thread Uwe Menges
On 10/17/18 10:37 PM, Ashwin Krishna wrote:
> The previous call was to understand the pain points of the community
> in general for governance and contributions. Based on the feedback
> from those who attended, we have come up with the action plan as
> mentioned in the previous mail and we will drive it.

[BUMP]

I didn't see a very concrete action plan with responsibilities or dates
in the previous e-mail.

I don't know anything about the situation at BETSOL, Zmanda, JLM with
regards to staffing and funding for the amanda / Zmanda development (or
in general). Or how the development process used to be, besides what can
be seen on github.

So here's my 2ct.

As the meeting minutes state and others already pointed out we should
probably use github with wiki. So someone with access rights should tick
[x] Wikis on github's Settings page and/or enable Pages. AFAICS there
are two people, martineau and NingZhangWisc according to
.

ASAP you (or we?) should find someone to enable small PR merges so eg.
Dustins fix PR#92 and others can get into a minor version bump later.

There probably needs to be a software architect that decides directions
for heavier things like Chap's PR#78. Is there one? Are there (paid?)
people working on github issues?

The suggestions from Dustin were also good and should find their way in
some kind of roadmap (which could be a simple .md on github).

Some eg. monthly information for the community what's happening behind
the scenes would be nice.

Yours, Uwe





Re: Meeting Minutes : Amanda Open Source Community

2018-10-30 Thread Stefan G. Weichinger

Am 30.10.18 um 15:29 schrieb J Chapman Flack:

On 10/30/18 10:13 AM, Stefan G. Weichinger wrote:

Am 30.10.18 um 15:06 schrieb J Chapman Flack:

On 10/30/18 5:58 AM, Stefan G. Weichinger wrote:

Would it be feasible to just pick a date and retire the svn repo
and declare the github one to be the locus of development?


This has to be decided by the owner of Amanda, BETSOL, IMO.

And personally I am waiting for decisions and announcements like that.


I agree. Just suggesting an easily-implemented possibility 


I don't have a problem with github as the main project's platform.

I use it daily with various other projects ... everything can be 
discussed but for now I think the main priority should be getting the 
next patches into amanda asap.


Who and where is a developer from upstream that is reachable and 
communicates with the amanda-users in a reliable way?


JLM does not even discuss with us in this thread ... hello, anyone?


Re: Meeting Minutes : Amanda Open Source Community

2018-10-30 Thread J Chapman Flack
On 10/30/18 5:58 AM, Stefan G. Weichinger wrote:

> Provide an issue tracker etc ASAP for users to be able to contribute
> feature requests and patches etc

As there is already https://github.com/zmanda/amanda with an issue
tracker, wiki, pull requests, etc., and the full source history thanks
to mirroring svn ...

Would it be feasible to just pick a date and retire the svn repo
and declare the github one to be the locus of development?

-Chap


Re: Meeting Minutes : Amanda Open Source Community

2018-10-30 Thread J Chapman Flack
On 10/30/18 10:13 AM, Stefan G. Weichinger wrote:
> Am 30.10.18 um 15:06 schrieb J Chapman Flack:
>> On 10/30/18 5:58 AM, Stefan G. Weichinger wrote:
>>
>> Would it be feasible to just pick a date and retire the svn repo
>> and declare the github one to be the locus of development?
> 
> This has to be decided by the owner of Amanda, BETSOL, IMO.
> 
> And personally I am waiting for decisions and announcements like that.

I agree. Just suggesting an easily-implemented possibility 


Re: Meeting Minutes : Amanda Open Source Community

2018-10-30 Thread Stefan G. Weichinger

Am 30.10.18 um 15:06 schrieb J Chapman Flack:

On 10/30/18 5:58 AM, Stefan G. Weichinger wrote:


Provide an issue tracker etc ASAP for users to be able to contribute
feature requests and patches etc


As there is already https://github.com/zmanda/amanda with an issue
tracker, wiki, pull requests, etc., and the full source history thanks
to mirroring svn ...

Would it be feasible to just pick a date and retire the svn repo
and declare the github one to be the locus of development?


This has to be decided by the owner of Amanda, BETSOL, IMO.

And personally I am waiting for decisions and announcements like that.


Re: Meeting Minutes : Amanda Open Source Community

2018-10-30 Thread Stefan G. Weichinger

Am 17.10.18 um 22:37 schrieb Ashwin Krishna:

So is Jean-Louis still involved or not? Employed by Betsol or ...
?


Jean Louis is not with BETSOL. He is part of the community though. 
The previous call was to understand the pain points of the community

in general for governance and contributions. Based on the feedback
from those who attended, we have come up with the action plan as
mentioned in the previous mail and we will drive it.


What features do we need, is there a plan to further migrate to
perl code, what are the platforms covered, etc


As we have been with Amanda for a very short time, we will gradually
get there. Meanwhile, any of the existing members want to take up the
initiative to drive this?


Define "this".

Provide an issue tracker etc ASAP for users to be able to contribute 
feature requests and patches etc


We all wait and have numerous things to report etc

AND: communicate! reply!

See this list, 3 or more issues since your last posting, no upstream 
developer has replied so far, right?


Stefan


Re: Meeting Minutes : Amanda Open Source Community

2018-10-18 Thread Gene Heskett
On Thursday 18 October 2018 09:28:31 Dustin J. Mitchell wrote:

> Hi!  I hacked on Amanda for a while before joining Mozilla 8 years ago
> (today!).
>
> While I was at Zmanda I worked pretty hard to keep the project
> accessible to non-employees.  While we did have a solid core of
> helpful power-users, substantial code-related participation was rare
> at best.  I think there were a variety of reasons for that, and some
> of the work we did aimed to change it (rewriting from C to Perl, and
> specifically the Application API).  But at least in my time it never
> really took off.
>
> I also see that Amanda itself has not seen a lot of work recently --
> the most recent commit is in February.
>
> I would suggest a few things:
>  * Focus on the strengths -- perhaps form some kind of advisory
> council comprised of long-time community members that can give
> guidance on project direction.  I know that's a little scary for a
> company, but "advisory" is a little softer than "governance".  That
> group could probably advise on the remainder of my suggestions.
>  * Put the code on Github.  Maybe it feels like selling out, but
> that's a massively lower bar to entry than sourceforge / svn. 
> Buildbot did this about 10 years ago and the bump in participation was
> massive. * Set up some kind of public CI -- maybe Travis is enough, or
> maybe set up Buildbot (or Taskcluster.. I feel obligated to say
> that..)
>  * Actively groom casual contributors:
>* Set up "good first bug" tagged issues -- tasks with small scope
> that can be accomplished by a newcomer in a day or two
>* Participate in programs like GSoC, Outreachy, GCI, or host
> hackathons at relevant conferences
>* Provide a simple, well-tested getting-started-hacking guide
>
> Somewhat longer-term, it might be good to talk about what Amanda wants
> to be.  Amanda's *old* - 26 years old!  What is its specialty in the
> modern, cloud-driven era?  With limited development resources, it
> doesn't make sense to pretend Amanda is good for things where it is a
> bad fit.

IMO the judgement of its being a bad fit is entirely in the mind of the 
local administrator. An educational package of docs aimed at that person 
is 20+ years overdue. 
>
> Dustin

Coming from you Dustin, thats great advice. IMO while you were working on 
it, some real progress was made.


Copyright 2018 by Maurice E. Heskett
-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


Re: Meeting Minutes : Amanda Open Source Community

2018-10-17 Thread Gene Heskett
On Wednesday 17 October 2018 16:37:04 Ashwin Krishna wrote:

> >So is Jean-Louis still involved or not? Employed by Betsol or ... ?
>
> Jean Louis is not with BETSOL. He is part of the community though.

Putting him on the payroll would be the right thing to do. Then don't 
micro-manage him, let him do what he does best.

> The previous call was to understand the pain points of the community
> in general for governance and contributions. Based on the feedback
> from those who attended, we have come up with the action plan as
> mentioned in the previous mail and we will drive it.
>
> >What features do we need, is there a plan to further migrate to perl
> > code, what are the platforms covered, etc
>
> As we have been with Amanda for a very short time, we will gradually
> get there. Meanwhile, any of the existing members want to take up the
> initiative to drive this?
>
> Regards,
> Ashwin Krishna
>
> -Original Message-
> From: owner-amanda-us...@amanda.org  On
> Behalf Of Stefan G. Weichinger Sent: Wednesday, October 17, 2018 1:53
> AM
> To: amanda-users 
> Subject: Re: Meeting Minutes : Amanda Open Source Community
>
> Am 16.10.18 um 21:39 schrieb Ashwin Krishna:
> > Meeting Minutes : [10/08/2018] : Connect with Amanda Open Source
> > Community
> >
> >
> > §Jean-Louis had served that role over the last few years.
> >
> > §Over the last decade Jean-Louis from Zmanda has been doing it.
> >
> > §wiki.zmanda.com : Hosted by Zmanda.Inc [now BETSOL]
> >
> > §amanda-core team and Jean-Louis are aware of the process.
>
> So is Jean-Louis still involved or not? Employed by Betsol or ... ?
>
> I think this is a crucial point, as JL was the main dev (from point of
> view of the OSS community of Amanda) in the last years.
>
> Some of the other mentioned points read like "sure, headings" ;-) I
> completely miss any *goals* for the project aside from where and how
> to host code and docs (important as well, sure).
>
> What features do we need, is there a plan to further migrate to perl
> code, what are the platforms covered, etc
>
> Do you agree, amanda-users?



Copyright 2018 by Maurice E. Heskett
-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>



Re: Meeting Minutes : Amanda Open Source Community

2018-10-17 Thread Nathan Stratton Treadway
On Wed, Oct 17, 2018 at 20:37:04 +, Ashwin Krishna wrote:
> Meanwhile, any of the existing members want to take up the initiative
> to drive this?

Just to push a little harder on this point:

Based on this email and earlier discussion, it seems like BETSOL is
working hard to include the "existing" Amanda developer community as
they proceed to figure out what it means to take over the Zmanda
organization.

This is certainly would be great opportunity to start including external
developers in the Amanda development cycle -- but only if such people
actually do exist at this point in time...

So, I guess my question for the group here is whether there are in fact
any people out there who are interested in re-constituting what used to
be the Amanda "core" team (in the short term)?

If there are, that is great and they can start working with BETSOL right
away

... but if there aren't, it would be nice to sort of establish that
publicly, so that BETSOL can change their approach a bit and proceed
quickly to get development moving forward again without waiting for
external involvement (at least in these early stages -- certainly
there's lots of room for external involvement once development has
restarted).

Thoughts?

Nathan

p.s. for completeness, adding a CC to the amanda-hackers list


Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239


RE: Meeting Minutes : Amanda Open Source Community

2018-10-17 Thread Ashwin Krishna
>So is Jean-Louis still involved or not? Employed by Betsol or ... ?

Jean Louis is not with BETSOL. He is part of the community though.
The previous call was to understand the pain points of the community in general 
for governance and contributions. Based on the feedback from those who 
attended, we have come up with the action plan as mentioned in the previous 
mail and we will drive it. 

>What features do we need, is there a plan to further migrate to perl code, 
>what are the platforms covered, etc

As we have been with Amanda for a very short time, we will gradually get there. 
Meanwhile, any of the existing members want to take up the initiative to drive 
this?

Regards,
Ashwin Krishna

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Stefan G. Weichinger
Sent: Wednesday, October 17, 2018 1:53 AM
To: amanda-users 
Subject: Re: Meeting Minutes : Amanda Open Source Community

Am 16.10.18 um 21:39 schrieb Ashwin Krishna:
> Meeting Minutes : [10/08/2018] : Connect with Amanda Open Source 
> Community
> 
> 
> §Jean-Louis had served that role over the last few years.

> §Over the last decade Jean-Louis from Zmanda has been doing it.

> §wiki.zmanda.com : Hosted by Zmanda.Inc [now BETSOL]

> §amanda-core team and Jean-Louis are aware of the process.

So is Jean-Louis still involved or not? Employed by Betsol or ... ?

I think this is a crucial point, as JL was the main dev (from point of view of 
the OSS community of Amanda) in the last years.

Some of the other mentioned points read like "sure, headings" ;-) I completely 
miss any *goals* for the project aside from where and how to host code and docs 
(important as well, sure).

What features do we need, is there a plan to further migrate to perl code, what 
are the platforms covered, etc

Do you agree, amanda-users?



Re: Meeting Minutes : Amanda Open Source Community

2018-10-17 Thread Gene Heskett
On Wednesday 17 October 2018 03:53:14 Stefan G. Weichinger wrote:

> Am 16.10.18 um 21:39 schrieb Ashwin Krishna:
> > Meeting Minutes : [10/08/2018] : Connect with Amanda Open Source
> > Community
> >
> >
> > §Jean-Louis had served that role over the last few years.
> >
> > §Over the last decade Jean-Louis from Zmanda has been doing it.
> >
> > §wiki.zmanda.com : Hosted by Zmanda.Inc [now BETSOL]
> >
> > §amanda-core team and Jean-Louis are aware of the process.
>
> So is Jean-Louis still involved or not? Employed by Betsol or ... ?
>
> I think this is a crucial point, as JL was the main dev (from point of
> view of the OSS community of Amanda) in the last years.
>
> Some of the other mentioned points read like "sure, headings" ;-) I
> completely miss any *goals* for the project aside from where and how
> to host code and docs (important as well, sure).
>
> What features do we need, is there a plan to further migrate to perl
> code, what are the platforms covered, etc
>
> Do you agree, amanda-users?

Yes. JLM has been known to me for most of the 20 years I've been using 
it, and likely knows more about its innards than anyone else. We know 
you, Stefan, but not for as long as JLM.

As for what it needs? A planner that actually does what its said to do is 
one of the higher priorities. An estimator thats trustworthy so we 
aren't forced to use the swag's we are using now would also be nice.
With a 7 day cycle, it acts like a 2 day cycle, promoting stuff from 6 
days head several times in that 7 days.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: Meeting Minutes : Amanda Open Source Community

2018-10-17 Thread Stefan G. Weichinger

Am 16.10.18 um 21:39 schrieb Ashwin Krishna:

Meeting Minutes : [10/08/2018] : Connect with Amanda Open Source Community


§Jean-Louis had served that role over the last few years.



§Over the last decade Jean-Louis from Zmanda has been doing it.



§wiki.zmanda.com : Hosted by Zmanda.Inc [now BETSOL]



§amanda-core team and Jean-Louis are aware of the process.


So is Jean-Louis still involved or not? Employed by Betsol or ... ?

I think this is a crucial point, as JL was the main dev (from point of 
view of the OSS community of Amanda) in the last years.


Some of the other mentioned points read like "sure, headings" ;-) I 
completely miss any *goals* for the project aside from where and how to 
host code and docs (important as well, sure).


What features do we need, is there a plan to further migrate to perl 
code, what are the platforms covered, etc


Do you agree, amanda-users?


Re: Meeting Minutes : Amanda Open Source Community

2018-10-16 Thread Charles Curley
On Tue, 16 Oct 2018 19:39:12 +
Ashwin Krishna  wrote:

> Meeting Minutes : [10/08/2018] : Connect with Amanda Open Source
> Community

Thank you, sir.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
https://charlescurley.com


Meeting Minutes : Amanda Open Source Community

2018-10-16 Thread Ashwin Krishna
Meeting Minutes : [10/08/2018] : Connect with Amanda Open Source Community

· Acquisitions by BETSOL in the backup space:

§  REBIT : https://rebitgo.com/

§  ZMANDA :  https://www.zmanda.com

§  Acquisition of Zmanda from Carbonite and transition of Zmanda sales team 
completed.



· Discussed the existing governance model for open source community to 
identify the pain points :

§  Gatekeepers for the project :- [Review and Merge commit requests, Resolving 
bugs, Plan releases]

§  Jean-Louis had served that role over the last few years.

§  Open Source Code Documentation :- [man pages, readme docs, release notes]

§  amanda-core team used to maintain until Zmanda came into picture.

§  Over the last decade Jean-Louis from Zmanda has been doing it.

§  wiki.zmanda.com : Hosted by Zmanda.Inc [now BETSOL]

§  Release process :

§  amanda-core team and Jean-Louis are aware of the process.

§  Again Jean-Louis has taken care of it over the years.

§  No documentation available for the release process.

§  Maintaining and updating amanda website.

§  Source Code for Website available on amanda SVN : 
https://sourceforge.net/p/amanda/www/HEAD/tree/

§  Mailing Lists  :

§  Hosted by Todd [one of amanda-core team members]

§  forums.zmanda.com : Hosted by Zmanda.Inc [now BETSOL]


· Suggested Changes to the Governance Model :-  [Please voice your 
opinions on the below]

§  Transition Amanda repository to Github to bring all project management 
activities under a single roof.

§  Hosting Amanda.org - Github Pages

§  Hosting documentation - Github Pages, Wikis

§  Code review and Merge requests

§  Raise questions or bugs.

§  Milestones and release planning.

§  Make Sourceforge ReadOnly.

§  Existing Amanda repo on Github is under Zmanda : https://github.com/zmanda/

§  Continue with the same OR move it to a new project.

§  Identify new Gatekeepers for Amanda

§  BETSOL to identify developers for the task.

§  Volunteers who are familiar with amanda core needed from Community

§  Volunteers to help in the transition process

§  Transition plan

§  Amanda Website

§  Documentation & Wiki pages

§  Document Release process

§  Volunteers for Technical Seminars of existing source code for knowledge 
sharing among members.



· BETSOL's Commitment to Open Source

§  Contribute to Open Source Community [One of them to be part of Gatekeepers - 
to be identified]

§  We have been offering scholarships and internship opportunities over the 
years at universities. (Colorado State University, Kansas State University and 
Colorado School of Mines).
In 2019, we are offering scholarships to involve and bring student 
participation to Amanda.

[-Ashwin] : We have a small dedicated team today and we have been constantly 
adding new members.
I'll be sharing Itemized list of tasks that needs to be worked on for Github 
transition.
Please reach back to us if you think you can help with any of the tasks.
I don't have the recording handy with me right now. I'll get it and share it 
here.