Re: Managing accounts/passwords for the Fineract project

[Ebenezer Graham]

Hi Myrle,

Thanks for looking it to this.

Bitwarden would have been perfect but one thing I noticed is that the free
offer has the following limitations

FreeFor testing or personal users to share with 1 other user.• Limited to 2
users (including you)• Limited to 2 collections

I second the idea of keeping it in the private area for now. I will
continue to look out for ways to securely share the password

*At your service,*

*Ebenezer Graham*

*BSc (Hons) Computing*


[image: EmailSignature.png]

African Leadership University,

Power Mill Road, Pamplemousses,

Mauritius.


​
*skype*:
​ebenezer.graham
GitHub  | LinkedIn
 | Twitter
 | Facebook

www.pactmart.com | Freelancing made easy.


*“Talk is cheap, show me the code.” *- *Linus Torvalds*



On 24 August 2018 at 19:16, Aleksandar Vidakovic 
wrote:

> Hi Myrle,
>
> ... there is also Bitwarden (https://bitwarden.com/) which:
>
>- is open source
>- available as a commercial offer or for self hosting (they have Docker
>images as far as I remember)
>- available for pretty much any platform (mobile, desktop, browser, cli)
>- as far as I'm aware it should be at least on par feature wise with
>Last Pass and similar services
>- I think it had some good reviews
>
> Cheers,
>
> Aleks
>
> On Fri, Aug 24, 2018 at 5:08 PM Myrle Krantz  wrote:
>
> > Hey all,
> >
> > I asked on the Apache comdev list about other ideas for how to manage
> > passwords and accounts:
> >
> >
> > https://lists.apache.org/thread.html/62bfb3a74484312afb4f9eb2387a6f
> 58ea36e20a171d88fdb785378c@%3Cdev.community.apache.org%3E
> >
> > Ideas included:
> > * using an svn private area
> > * using an svn private area and encrypting the password with the keys
> > of the PMC members
> > * using LastPass (and paying 48$ for it)
> > * using https://www.passwordstore.org/
> > * asking one of the password managers for freebies
> >
> > We are only talking about one account with low value at this point.
> > And I don't think most of our committers know how to use svn (or are
> > particularly motivated to learn).  Given those facts, I recommend we
> > continue to use our confluence private area for now.
> >
> > If anyone else has ideas or preferences, I welcome them.
> >
> > Best Regards,
> > Myrle
> >
>

Arabic Language

[Naser Abdelati]

Re: fineract'ers

[Myrle Krantz]

Hey all,

Just FYI, I forwarded James Dailey's mail to Ross, and here was his
response.  (There's a little plug in there for ApacheCon as well.
Anyone who hasn't registered yet: there's still time. : o)

"Thanks Myrle,

You are correct I do not actively follow the Fineract dev list
anymore. Feel free to share this back to the broader community list if
it helps.

The below email from James is a good summary of our conversation at
OSCON. This conversation was a general one about “The Apache Way” and
how Apache projects deal with growing pains as their code matures. I
cannot comment on how well James has applied those general lessons to
Fineract today, but I certainly see plenty of good content within this
mail.

If I were to summarize that general guidance in a few sentences it
would be to remove as much friction from the contribution process
(code reviews, merit recognition, community alignment) as possible.
Generally speaking the lower the barriers to contribution the faster
the community will grow. This does depend on people actively
monitoring the project, but monitoring is less work than gate-keeping.

Adopting things like Lazy Consensus can be key
http://community.apache.org/committers/lazyConsensus.html.

In the days of SVN we were forced by the tooling to operate with a
branching model. This works really well. All changes are visible in
one place. Work in progress can be easily discovered and reviewed. It
means those monitoring the project have the opportunity to review work
as it happens, thus enabling them to raise concerns about a design
decision or implementation weakness early in the process. This in turn
meant that when it was time to consider a merge most of the rough
edges had ben talked about *before* they had become deeply imbedded in
finished code. It was easier to fix and people would work together to
design a fix that worked for everyone.

As James indicates Git does not force this way of working. It has
excellent support for the SVN concept of branching, unfortunately
GitHub has driven most people to click “fork” (mostly invisible to the
community) rather than branch. GitHub, therefore, has encouraged us to
work privately then issue a pull request for review when the work is
“finished”. This often means people are not keen to redo their
implementation to satisfy the broader needs of the community. They
will blame the community for “blocking” their improvements.

I am a strong believer in doing as much as possible in the open at all
times and reducing barriers to collaboration.

Interestingly, I have a talk on this topic at ApacheCon this year, if
only I’d written it already

Ross"
On Wed, Jul 25, 2018 at 7:00 PM James Dailey  wrote:
>
> Hi All -
>
> For the good of this project, I'd like to share some ideas gathered and
> shared in a side meeting at OSCON18 with Apache President Ross Gardler who
> was one of the champions of this project.  You can read the official PMC
> reports that go to the Apache Board here -->
> https://cwiki.apache.org/confluence/display/FINERACT/Board+Reports
>
> I am not a member of the PMC, nor a committer, but I have been involved
> from the beginnings of this in 2002. So, I am hoping to share both the
> short term and the long term view.  As most of you know, the Mifos
> Initiative contributed the code to Apache and remains - as an external
> entity - highly interested in ensuring the continuation and growth of the
> project.  In the Apache worldview, Mifos offers a kind of "productization"
> of the *project*, and the hope is that many more such entities - for profit
> companies in particular - will productize, and contribute back via the
> community of developers, requirements and ideas.  In other projects we know
> within Apache, contributors can be paid by companies to make sure that
> their priorities get attention. Those companies and entities provide a kind
> of "wrapper" around the project and can provide things like dashboards,
> add-ons, and deployment scripts.  Thus a virtuous cycle is born and
> supported.
>
> What we do not want, and must try to avoid, are hard forks by the users
> (entities that take the code and deploy in the real world), where they have
> long standing unmerged changes, and worst that these changes are
> incompatible with the upstream changes that are on the main fineract dev
> branch. This then leads to harder to maintain code at the users and more
> costly duplicative development for all. This is the opposite of the
> virtuous cycle.
>
> If there are large unmerged changes that can be proposed for either
> Fineract1.x or for Fineract-CN, I believe a key way forward would be to
> make those branches visible. Fortunately, and tongue firmly in cheek, there
> is a mechanism available in git conveniently called a "branch".  I think
> the PMC should consider this approach to bring into the fold those outside
> entities that are on forks (via the individual contributors) and then to
> have a clear process by which a serious attempt 

Fwd: Apache Track online at Solutions.Hamburg 2018

[Myrle Krantz]

Chris and I are still looking for people to party with us at the best
business party in Germany.

If you don't believe us ask anyone else who was there last year
(Sharan or Greg or Justin or Lars or Mark or Benedikt or Mark).  I ate
crocodile for the first time and played kicker all night.

Solutions.hamburg is a major conference in Germany at the intersection
of technology and business.  It's a great opportunity to get out the
word about Apache and to network.  Please come and help us (wo)man the
booth.

Greets,
Myrle

-- Forwarded message -
From: Christofer Dutz 
Date: Mon, Jul 30, 2018 at 3:20 PM
Subject: Apache Track online at Solutions.Hamburg 2018
To: d...@community.apache.org 


Hi all,

so it seems we finally have the schedule for the Apache track online:
https://solutions.hamburg/track#396deb5f-626f-11e8-ac7b-30c85c7536af

Just 3 tiny talks, but the biggest win is our free ASF Booth … still
looking for some people willing to help out with staffing the booth
(we got it for all 3 days) …
and if I haven’t mentioned … you get a free ticket for a great party ;-)

Chris

Re: Managing accounts/passwords for the Fineract project

[Aleksandar Vidakovic]

Hi Myrle,

... there is also Bitwarden (https://bitwarden.com/) which:

   - is open source
   - available as a commercial offer or for self hosting (they have Docker
   images as far as I remember)
   - available for pretty much any platform (mobile, desktop, browser, cli)
   - as far as I'm aware it should be at least on par feature wise with
   Last Pass and similar services
   - I think it had some good reviews

Cheers,

Aleks

On Fri, Aug 24, 2018 at 5:08 PM Myrle Krantz  wrote:

> Hey all,
>
> I asked on the Apache comdev list about other ideas for how to manage
> passwords and accounts:
>
>
> https://lists.apache.org/thread.html/62bfb3a74484312afb4f9eb2387a6f58ea36e20a171d88fdb785378c@%3Cdev.community.apache.org%3E
>
> Ideas included:
> * using an svn private area
> * using an svn private area and encrypting the password with the keys
> of the PMC members
> * using LastPass (and paying 48$ for it)
> * using https://www.passwordstore.org/
> * asking one of the password managers for freebies
>
> We are only talking about one account with low value at this point.
> And I don't think most of our committers know how to use svn (or are
> particularly motivated to learn).  Given those facts, I recommend we
> continue to use our confluence private area for now.
>
> If anyone else has ideas or preferences, I welcome them.
>
> Best Regards,
> Myrle
>

Apache project logos central

[Myrle Krantz]

Hey all,

This is a really cool thing being put together on comdev by Daniel
Gruno.  If you're looking for an Apache logo for a presentation or the
like this would be an excellent place to look for it.

And to whoever uploaded the Fineract logo, thank you!

Best Regards,
Myrle

-- Forwarded message -
From: Daniel Gruno 
Date: Fri, Aug 24, 2018 at 2:39 PM
Subject: Update on logo hunt
To: 


Hi all,

Logos are slowly ticking in and being processed.
I have a mockup of a 'logo central' site working, which you can see at
https://logos.humbedooh.com/ - it has all the images that are available
on scalable formats (svg, eps, ai etc) with various versions available.
Images are automatically processed from SVN every hour on the hour, so
any new additions should show up within an hour.

I'll work on adding a "how do I submit my logo" part of this as time
permits. Hopefully this will spur some more logos being added :) And if
enough traction, we can put this and the automated process on a comdev VM.

With regards,
Daniel.

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

Managing accounts/passwords for the Fineract project

[Myrle Krantz]

Hey all,

I asked on the Apache comdev list about other ideas for how to manage
passwords and accounts:

https://lists.apache.org/thread.html/62bfb3a74484312afb4f9eb2387a6f58ea36e20a171d88fdb785378c@%3Cdev.community.apache.org%3E

Ideas included:
* using an svn private area
* using an svn private area and encrypting the password with the keys
of the PMC members
* using LastPass (and paying 48$ for it)
* using https://www.passwordstore.org/
* asking one of the password managers for freebies

We are only talking about one account with low value at this point.
And I don't think most of our committers know how to use svn (or are
particularly motivated to learn).  Given those facts, I recommend we
continue to use our confluence private area for now.

If anyone else has ideas or preferences, I welcome them.

Best Regards,
Myrle