it was not supposed to 'claim' work ... and I'll use the githup repo for the
work so we all can work on it ... this is usually how to collaborate on code
but I think it is good style to 1. let others know that something happens, and
2. have a poont of reference ...
Cheers
Markus
::: YAG
thanks for the feedback ... I think jira issues are simply a good way of
organizing work ... you see what is going on w/out reading a bunch email
threads.
The sample commit message I've used was directly copied from the ASF
documentation ... but I'm fine doing a commit instead of pre calling
awesome ... now we only wait for infra to setup our Confluence space ... then
we are ready to rock ; o)
Best,
Markus
.:: YAGNI likes a DRY KISS ::.
On Sat, Dec 26, 2015 at 11:52 AM -0800, "Roman Shaposhnik"
wrote:
Fixed.
On Sat, Dec 26, 2015 at 7:48 AM, Markus Geiß wrote:
>
haha ... good to know ... I'll add it tomorrow in my morning hours ...
Best
Markus
.:: YAGNI likes a DRY KISS ::.
On Sat, Dec 26, 2015 at 11:57 AM -0800, "Roman Shaposhnik"
wrote:
Guys,
congrats on a nicely looking website! One think
that I've noticed is that the Incubator dis
mage ... I only needed to use a different one for JIRA ...
Best,
Markus
Cheerio
Markus
::: YAGNI likes a DRY KISS :::
On Sun, Dec 27, 2015 at 11:43 AM -0800, "Roman Shaposhnik"
wrote:
On Sun, Dec 27, 2015 at 3:57 AM, Markus Geiß wrote:
> Hey,
>
> I've tried to edit the hom
I've read this, and the general branding stuff ... once we have pulled your
changes to the website ... I'll add some reference links ...
Best,
Markus
.:: YAGNI likes a DRY KISS ::.
On Sun, Dec 27, 2015 at 11:38 AM -0800, "Roman Shaposhnik"
wrote:
On Sat, Dec 26, 2015 at 11:55
Hey all,
happy new year!
I simply volunteered some of my time to kickstart our initiative to become an
Apache project.
I don't consider myself as 'El Capitan', or any special role at all. I'm part
if this community, extremely excited, and happy that we have this opportunity
for Mifos.
Hey Ross,
happy new year!
How should we deal with the required sign-off? Should we assume consensus if we
don't here something and simply add a mentor to the sign-off list?
This feels a bit strange to me to be honest, but if you guys feel good about
that I'm fine.
Best,
Markus
.:: Y
immediate ... I've used bootstrap as a starting point ... ; o)
Best,
Markus
.:: YAGNI likes a DRY KISS ::.
On Fri, Jan 1, 2016 at 10:41 AM -0800, "Greg Stein" wrote:
How soon can we switch to Bootstrap?? :-)
On Fri, Jan 1, 2016 at 11:56 AM, Markus Geiss wrote:
> I guess the i
Hey Keith,
to answer your questions:
As a contributor you don't need to sign an iCLA, just fork the repo and you're
good to go.
For a local dev setup we already provide an embedded run config, let me check
the current documentation and add an how to tomorrow.
Only the back end/platform
Hey Keith,
thanks for the feedback, I'll edit the page to add more clarification.
If you take a look at the files you'll find two additional files parallel to
the build.gradle. By default all dependencies of production.gradle are used.
Changing this in gradle.properties with env=dev will po
Hey Vishwas,
The repackeging led to a delete and add of all files anyways, so a simple fetch
merge could cause more harm than the creation of a new fork and manually
transfer made changes to the code that never where contributed back.
In addition I'd suggest to do future code enhancements i
In addition we will honor Contributors more prominent in the future with a
special thank you section at the website and for sure will add all current
contributors there too.
Best,
Markus
.:: YAGNI likes a DRY KISS ::.
On Fri, Jan 29, 2016 at 9:59 PM -0800, wrote:
Hey Vishwas
I can understand your concern ... and if we agree on doing so ... I'm fine with
reverting the changes ... clean the repo again ... and pull in develop only ...
I did not say that keeping the history in general is a risk, all I've said is
keeping the history as it is now holds some risk.
Asi
Hey Adi,
this sounds like a good approach. Don't feel pressured to do it over the
weekend. Take your time to do needed adjustments and if it is mid of next week
this us fine too!
If we now do this, let's make it clean and right. Do the changes, send a pull
request, and let's merge it into
Thanks for the clarification ...
Best,
Markus
.:: YAGNI likes a DRY KISS ::.
On Sat, Jan 30, 2016 at 6:43 AM -0800, "Greg Stein" wrote:
The ASF has zero problem if version control contains history that does not
conform to its policies.
The "rules" really come into play when a s
16 matches
Mail list logo
