[sr] Seamonkey Serbian translation - tracking bug

RESOLVED INVALID

Status

RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: Milos, Assigned: Milos)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

9 years ago
This is tracking bug for SeaMonkey Serbian translation. Links to all related bugs go here.

Updated

9 years ago
Duplicate of this bug: 305892

Comment 2

9 years ago
Milos, it makes more sense to not open a new bug for this, since there is a lot of context in the older one.  Please consider that.  I won't interfere in what you ultimately do, but my recommendation is indeed to revert.

Thanks,
f
(Assignee)

Comment 3

9 years ago
(In reply to comment #2)
> Milos, it makes more sense to not open a new bug for this, since there is a lot
> of context in the older one.  Please consider that.  I won't interfere in what
> you ultimately do, but my recommendation is indeed to revert.
> 
> Thanks,
> f

Following other ppl examples, I don't like reopening more than a year old bugs. Other than that, that bug has some comments that shouldn't be there, in terms of that conversation should go somewhere else, not on the bug we started 'cause I said I have the team to help me translate seamonkey.

If you don't mind(Nikola too) I'd like to use this bug only for tracking our progress in trasnlation of SeaMonkey, and not for argues about this kind of things. Everybody is free to open a new bug to argue about who should be translation coordinator, how should we work, what we should and what we shouldn't do etc... This bug is intended just for tracking and allowing future contributors to get involved more easily(having in mind that they might not wanna read our argues - I know I wouldn't).

So please, if any of you see the need to still argue about this, file a new bug.
(Assignee)

Updated

9 years ago
Keywords: productization

Comment 4

9 years ago
We already have a bug about Seamonkey translation. 

I think that talks about translation should be in one place, not scattered on all new bugs (including this one), anyone would like to start at a random time.

Also committing translations should not be separated from the discussion.
If it is done that "government" way, commits will vastly differ from translation community work and what is agreed upon on main bug report, that is #305892
(Assignee)

Comment 5

9 years ago
(In reply to comment #3)
> (In reply to comment #2)
> > Milos, it makes more sense to not open a new bug for this, since there is a lot
> > of context in the older one.  Please consider that.  I won't interfere in what
> > you ultimately do, but my recommendation is indeed to revert.
> > 
> > Thanks,
> > f
> 
> [...]
> If you don't mind(Nikola too) I'd like to use this bug only for tracking our
> progress in trasnlation of SeaMonkey, and not for argues about this kind of
> things. Everybody is free to open a new bug to argue about who should be
> translation coordinator, how should we work, what we should and what we
> shouldn't do etc... This bug is intended just for tracking and allowing future
> contributors to get involved more easily(having in mind that they might not
> wanna read our argues - I know I wouldn't).
> 
> So please, if any of you see the need to still argue about this, file a new
> bug.

Please read this.
(Assignee)

Comment 6

9 years ago
@maletaski,

are you still in? Nikola is out of the team.

Comment 7

9 years ago
Yes i am still in.

Updated

9 years ago
Duplicate of this bug: 305892

Comment 9

9 years ago
Milos Dinic Just deleted my big text I was making for translation on forum.
I think such behavior is truely unexceptable.
I truely think Milos Dinic is currently incapable of making organisation of Seamonkey translation.
He just decided: "Nikola is out of team". ??? I say, Milos is out of sense.

Comment 10

9 years ago
There is a bug thet will be used for project discussion and coordination, instead of this Tracking bug: Get discussion to: Bug #305892 Bug 305892
(Assignee)

Comment 11

9 years ago
First of all, I have putted you out of a team because you said very bad things about me on our forum, and showed what are you plans on how to do this. As I said, such a behavior is unacceptable in our team, and you're out. If you want to argue about who will be coordinator of this translation, please use another bug or send an email to Robert Kaiser, and don't post notices in this bug that might make other users think like you're allowed to do such things.

PLEASE

Comment 12

9 years ago
Mostly I think it is inappropriate for you to decide who and who will not translate Seamonkey. 
I ask you not to use this bug report (tracking bug) to argue anymore. We have all discussion about translation at Bug 305892 as >You< requested.

You will continue to receive bad reports because you continue to act bad toward me, trying to destroy effort in its infancy, trying to remove me from translation process and frankly I find you Fully incompetent to organize translation following your unappropriated <deleting> actions i past few days. 
You deleted tons of of documentation, trying to undermine my work.

You are NOT the only one who is working on translation and all must be made with an argument.

You are still here because you acquired our _Support_ to start a team in one moment. I am In the team now and only thing you can do is to step up and form some other team on some other project if you changed your mind about your role in a process and suddenly decided to change our positions.

Someone you might argue you misused team support to make your position where it is now and NOW you are trying to get rid of team members.

You are making this thing very difficult with your attitude.
You want to monopolize our efforts, ordering around on a firs HOUR of a process and you have no right to do so, we did not give you that right.

Please Stay with a bug 305892 for discussion and use this bug for what it is: Tracking Bug.
(Assignee)

Comment 13

9 years ago
I'm not the component owner anymore. Closing this one.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.