That seems also a good idea to me
Jacques
Le 18/08/2016 à 08:25, Nicolas Malin a écrit :
I agree with your remark Scott
Nicolas
Le 18/08/2016 à 07:28, Scott Gray a écrit :
Easy solution (if possible) would be to disable comments altogether. If
there's a discussion to be had about a page it
Pierre I think you workflow on your CI would be improve because I can't
understand why a svn up create a conflit only on regular change.
The conflit can appear only when you have local change and like taher
suggestn you need first update your ofbiz from a clean official copy and
after that dep
I agree with your remark Scott
Nicolas
Le 18/08/2016 à 07:28, Scott Gray a écrit :
Easy solution (if possible) would be to disable comments altogether. If
there's a discussion to be had about a page it can go to the dev list or
JIRA without risk of being deleted or creating any conspiracy theo
Agreed, the whole purpose of a wiki is to provide and organize information.
If we are going to worry about comments and "history" then we are using the
wrong tool for that. History is the last thing I would care about, instead
we should focus on having clean updated information.
On Aug 18, 2016 7:
Easy solution (if possible) would be to disable comments altogether. If
there's a discussion to be had about a page it can go to the dev list or
JIRA without risk of being deleted or creating any conspiracy theories
about censorship.
Being able to comment directly on a page is handy, but if we're
Hi Pierre,
I would also like to add that CD vs CI is irrelevant to my point. You would
still have an unstable trunk in both situations. The point emphasis is that
trunk is stable, not whether you're publishing or not.
Taher Alkhateeb
On Mon, Aug 15, 2016 at 9:38 PM, Pierre Smits
wrote:
> Hi Ta
You're correct. Not many deletions were done by non privileged
contributors, and as far as I can tell no non-privileged contributor ever
deleted the comment of another contributor.
Mostly they were done by privileged contributors on non open pages (in the
OFBIZADMIN space, meaning PMC Members). Wh
You are right, it should be moved to the open space. I'll wait a consensus before engaging more effort on this. Not only on the page itself but also
on the prioritized goals.
Jacques
Le 17/08/2016 à 20:01, Pierre Smits a écrit :
Is it in the right space? Where it is now, I would say it is a f
The idea is to focus team efforts on a small number of important goals rather
than scatter energies on a lot of small goals
To stay focused we need a Roadmap, a simple and realistic one.
Jacques
Le 17/08/2016 à 19:05, Taher Alkhateeb a écrit :
Hi Jacques,
Would you kindly clarify the object
Is it in the right space? Where it is now, I would say it is a fest of
privileged contributors.
Best regards,
Pierre
On Wednesday, August 17, 2016, Jacques Le Roux
wrote:
> Hi All,
>
> I move and replace the "Ofbiz Cookbook" thread from the user ML since it
> concerns more developers
>
> We ne
Hi Jacques,
Would you kindly clarify the objective of the roadmap? What is the desired
goal and how does it help? I think it is important to understand that to
see if I would invest time and effort towards authoring the work.
Taher Alkhatteb
On Aug 17, 2016 6:48 PM, "Jacques Le Roux"
wrote:
>
Hi All,
I move and replace the "Ofbiz Cookbook" thread from the user ML since it
concerns more developers
We need to have a very realistic lean Roadmap to agree on, follow and progress.
We can reuse https://cwiki.apache.org/confluence/display/OFBADMIN/New+Features+Roadmap+-+Living+Document by
I am not too much concerned about comments being deleted because the value
of comments should be transient (if not their content should be embedded in
the page).
For attachments I see that it would be an issue to loose them... but as far
as I remember we had no problems in the past so maybe we coul
As I explained below "Wed, Aug 17, 2016 at 12:51 PM", content is not a problem because it's still in page history or space trash. The problem is with
comments and attachments, see my previous explanation and question.
Maybe you implicitly agree about what I suggested about news, comments and
a
My preference is to let contributors to delete content, since this didn't
cause big problems until now; we may revisit this topic if we will
experience any problems in the future.
Jacopo
On Wed, Aug 17, 2016 at 4:06 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Jacopo,
>
> Thanks
Jacopo,
Thanks for the new thread creation. I wanted to relate the previous thread with my suggestion because of, IMO, the needed merge between the 2
"marketing pages".
Good idea about keeping the old spaces as archives w/o entering links.
With my suggestion I trust no Wiki space for the PMC
I am starting a new thread with a new subject in the dev list to discuss
the interesting topic about Wiki space cleanup/refactoring that was started
by Jacques as an off topic (going off-topic is a bad habit that we should
try to limit).
In my opinion we could just have one Wiki space (open to con
Agreed Sharan, it was just a try and it's not worth it for us. I just closed
it, thanks for checking!
Jacques
Le 17/08/2016 à 09:50, Sharan Foga a écrit :
Hi Jacques
I took a look at the Service Desk functionality you enabled in Jira and I'm not
sure that it fits the project flow. It seems t
Hi Jacques
I took a look at the Service Desk functionality you enabled in Jira and I'm not
sure that it fits the project flow. It seems to be focussed at customer service
desk resolution within agreed timeframes. Although you could argue that our
users are also our customers, no one is under an
Given this extra information â I think it would be good for the thanks link
to be the official ASF wide sponsors.
We can still look at discussing and creating a wiki thanks page for the project
itself as there seems to be some support for it and if agreed perhaps have a
prominent link in the
20 matches
Mail list logo