See my comments between the lines
Micha
That has nothing to do about “we” fill about it, we do the best with the
limited resources “we” have. You are always welcome to jump in and get part
of the “you guys”.
Please talk me through how you reasonably expect me to help you document
new product features that the only way I even know the existence of is
by… looking at the very docs I’m asking you to do a half-decent job of?
you already have a good knowlege of this new features in general and i
think you now get the specially the “static” modifier very good as we can
see in your blog post about this topic.
I think you need to stop swiveling things round to make it look like you
have a point. This specific example is aboutt he missing JSR-223 page, to
which your reply was “well people can help out with the docs”. Which I said
was a bit daft. In response you’re now talking about something else.
This is a bit disingenuous.
I did my best to at all information into the wiki on a bare minimum about
Lucee 5, if you see Gaps in this, you always can ping me, like i have
written more than once, but you answered me that this is not your job that
this is my job…
Like I have in this precise case. AND LOOK WHERE IT’S BLOODY GOT US!
There are a lot of TODO still in the Wiki about functonality you are well
aware off,
Note I’m not saying you need to furnish the final polished docs, just the
bare minimum docs for us to be able to be aware of the features, and
perhaps how to test them for you!
Come on mate, throw us a bone here. I’m trying to be part of the “we” but
you’re making it close to impossible.
Really! Are you kidding me, ok make a suggestion how you could help with
and how im stopping you to do so.
Don’t start with you first have to do all the work and i will polish it
then …
No. Start by saying “oh yeah, Adam: we’ve not done that page yet. We’re
actually having some problems with that feature so it’s not really ready
for testing yet”.
And at that point had you said “I’ve not got time to update the wiki page
right now”, I quite possibly would have said “yeah no worries mate, I have
it open in front of me and I’ll add a note”.
See? Easy.
And, yes, you’ve actually told us this now. But it took a bit of coercion,
didn’t it?!
Like I suggested, you would be doing yerself & Lucee a favour if you got
your nose out of BitBucket and the source code for a few days and got the
docs in shape so as to make it possible for people to actually work with
the beta,
i have spend 2 days only working on the Lucee 5 wiki entries, i have added
every Lucee 5 feature including simple code examples.
You simply don’t understand that i have limited resources on this and this
is not only because i have to work on the Lucee source code, this is
because i have also to make some money to survive.
I do understand you are a constrained resource (we get regular reminders).
However I do also see you fixing completely inconsequential “bugs” over
this period too. So my conclusion is that you’re perhaps not focusing where
your very limited resources ought be best applied. I could be wrong.
You have clarified a bit now, but this also took quite a while to coerce
out of you.
My Problem is not with that, it is how you tread the project, again it is
not only my impression that you are hurting the project with your
behaviour. I’m very serious about that!
Yes, and I think you (collectively) are hurting it too. I think you’re (ie:
Micha) doing your best, but there’s a bunch of other people in the LAS
who… don’t really seem to be helping out in areas that they have
expertise. And it’s not like anyone is seriously asking anyone outside of
LAS to pitch in and help in specific areas either. I know you’re busy,
but there’s a degree of “tough shit mate, it all still needs to be done”.
And I don’t mean that in a rude/mean way, it’s more driving home the point
that you being really busy and having only a finite resource is all well
and good, might be true, but it doesn’t help the situation.
And whilst you can say other ppl think the same about me, I know a bunch of
other people who agree with my position (and there’s actually some
overlap in that demographic too!)
That said, it’s not like we both aren’t correct in this regard.
Yeah the wiki entries are not professional, there is no company behind it
and pay the bills for everything.
I specifically made a point of saying “I don’t mean finished polished docs,
I just mean docs fit for a beta release”. Stop erecting strawmen by way of
justifying yourself. It won’t wash with me (you should know this by now).
So it is not helping if you write “you guys have to do every single piece
right …otherwise everything you do sucks”,
Again, I have not said that.
so if you find a problem in the doc ask me, i could explain you that
problem in seconds and you could do a decent blog post about the
functionality and not one that only shows what is not working.
As I said: this thread was me doing that. And look how well it went.
I’d fix the link to the JSR-223 page if I could find it.
There is still some problems with JSR223 that we have to solve first, so
having a doc public yet makes no sense.
OK. So why didn’t you just say that.
Then we only get a other blog post from you showing something that does
not work 
You can shove yer passive-aggressive smiley up yer arse mate. Seriously.
You’re taking the piss if you think you have legitimate justification for
giving me shit simply for writing up my findings, simply because my
findings don’t suit you.
Why not start to improve the static entry, you can for sure improve that a
lot and if you are not sure, ping me
I can add it to the list. I need to actually look at the stuff I’ve not
checked at all first.On Tuesday, 14 April 2015 15:11:20 UTC+1, Micha wrote:
On Tue, Apr 14, 2015 at 11:08 AM, Adam Cameron <camero...@gmail.com <javascript:>> wrote:
On Tuesday, 14 April 2015 01:52:21 UTC+1, Michael Offner wrote:
–
Adam