Assembla Team Rating
Notes
This team rating raised during the Assembla Rework Trac Update and showcases an important mechanism of the "Lazaridis System Design Audit Services".
The indenpendency of the executing analyst ensures intervention at any point where a stated project-directive is violated (here: Assembla/Breakout? directive "beeing honest"). A standard consultant would be afraid about the continuation of his job - and would most possibly not react in a manner best for the project/customers.
Case
During the Assembla Rework Trac, the Assembla Breakout team and the team lead stopped any interaction within the audited project (Breakout/Assembla?). This happend most possibly due to an activity trap within another project.
Several contributions of newcomers (looking for paid trials) remained unprocessed.
This led to the following ticket and related action:
Several private messages of the executing analyst were ignored, too, which led to this public message:
Despite some actions of the team and the team-lead within the project, all messages remained unanswered, which led to this question-ticket:
Again, all requests remained unanswered (which starts make a negative impression about the project).
Update Processing
The only private message was this of a team-member, who asked for the location of the assembla trac upgrade instructions. The answer was given within the relevant ticket 481.
Despite the stoped communication and payments, an important suggestion was given to the team:
- "The breakout production server should go initially only to 0.96."
This instruction was ignored, like all other planning/experiences, for which the assembla project has payed for (although reduced open-source rates).
This non-coordinated upgrade led to a system-failure:
- Can not access trac
- Re: Can not access trac (response from the responsible team member)
- TRAC and SUBVERSION error update (response from the team lead)
- Re: TRAC and SUBVERSION error update (response from the executing analyst)
The message from the executing analyst notifies the users about the real cause of the problems and asks for a statement - still without response.
Copyright Payment Guarantee
(this is an example case for the Copyright Payment Guarantee)
Copyright Violation: contributions made by "lazaridis_com"
After reminding about the copyright the tem lead contacts within private email.
It is very interesting that at this point there is still no public statement to the case.
The only public actions was closing the related ticket
The first public replies came in this thread:
- Copyright Violation - Please Remove my Contributions of Pay the Open Invoices
- further comments from the team lead
Interestingly, the team lead refers to the GPL (GNU Public License), which is non-existent within the breakout and the trac project.
The fact is, that all contributions remain under the exclusive copyright of the executing analyst.
Although the messages within assembla.com start to disappear, one more reminder:
Again silence.
At this point, an Assembla Partner is contacted and in another message, the team-lead is informed.
Simply, what's going on here - Google Cache