@add1sun - Sorry for this "Critical" but I really need some feedback.

It would be very helpfull for me in order to contribute more effectively know about some
default Doc management roles and maintenance tasks :

1. If I see some Nodes in Handbook that are to long and the add comments make a worth full report
on some Drupal technics related to the "Node" Title and I post an issue for requesting support/disregards
can I mid-while make the change because I'm 99% sure about approbation?

2. It's possible that I could be evaluate for approbation to edit my owns Issue text because
due to my weak english I discover that I made some mistakes and want to correct?

3. Do you think that the "Common expression & acronyms used on D.O. should be divided in 2 page ( dividing alphabet in two parts) for better consulting?

I know maybe this issue should be divided in more one's (is so please inform me) but as I see that You are the one almost more time answer my issue I really appreciate your opinions.

Thanks

Comments

add1sun’s picture

add1sun commented

hey wolfflow, thanks for all the work you have been doing. You are moving too fast for me to keep up. :-)

1. If you think something should be made into a new page or be edited, please do. If you aren't sure and you post an issue, but no one responds (in like a week or so) then just go ahead. Unfortunately people have scattered time to review issues. If you do something "wrong" or maybe a touch "off-base" then others can always point it out and and we can continue to refine and correct as we go.

2. As far as I know you can't edit issues because it could be confusing to the conversation if you change something. It is always better to correct by doing a comment and clarifying there. I know it is annoying but I end up doing the same thing too, even though I *can* edit my issues. Don't worry about your bad English. If we don't understand, then we can ask for clarification. (Either that or we will answer the wrong question and you can correct us with your real meaning.)

3. I'm not sure really. that is actually something I would like to ask the usability team or the redesign folks if they have a suggestion. It seems to me, personally, that having it all on one page is better. I like fewer clicks. :-)

As for separate issues, yes typically each thing should be its own issue. I feel like numbers 1 and 2 were both in the same area though and are fine together. Number 3 seems like a good pick to be its own issue so that others can discuss their preferences and ideas for the best approach.

I should also mention that I *try* to be active in the issue queue, but there will definitely be times when I am too busy to check in regularly so also feel free to ask these kinds of questions on the docs mail list. I hope that answers your questions. If not, please let me know and I will try to clarify.

Wolfflow’s picture

Wolfflow commented

@add1sun

Thank you very much for your feedback and explanations.
It feels good from time to time to be cleared in my doing here.

For answers:
on point 1- Ok fine everything clear
on point 2- Ok fine everything clear
on point 3- Ok I agree fully with you - (maybe the redesign Team could see later on how to improve -sooner or later)

Thanks you for your patience and "Yes I will try always to be as much clear as possible and give always additional
explanations if something is misunderstood.

Cheers

Wolfflow’s picture

Wolfflow commented
Status: Active » Closed (fixed)

This issue is clear to me, again thanks @add1sum for the feedback