twincling-triage — Twincling Triage project discussion list.

[triage] Triage

[sree c. <sre...@gm...>]

Hi All,
I was selected for Triage Project and eventhough i have been following
the mailing list,I have'nt been in touch actively through mails. I
would like to continue to be on Triage team and work on it.I am
wondering if we get to work on some of the  components/ modules or the
goals would be explicitly specified.Please let me know as i have
submitted Triage as my final year Project. Please let me know.

Thanks
Sreechand

Re: [triage] Database Design

[SMS <muk...@gm...>]

Hi Saifi,

I would like to move ahead with the Triage Project.Please let me know the
goals to be delivered and where we are going to start from. Looking forward
for your reply.

thanks,

SMS


On Thu, Oct 8, 2009 at 7:07 AM, Namita Iyer <na...@tw...> wrote:

> Hi Mukund,
>
> Based on your contributions done so far, here is the take.
>
> Twincling will be providing you mentoring for the month of October 2009.
> Certificate will be provided only if you are able to deliver on the goals
> discussed with the mentor (Saifi).
>
> thanks,
> Namita
>
>
>
> On Wed, 7 Oct 2009, SMS wrote:
>
>  Hi ,
>> Now that the unity prototype coding is complete and as far as the lift
>> deployment is concerned, i have deployed it .Yet there is still some error
>> though now i am able to see the Unity page and it works fine.Taking things
>> in triage ahead, when are we going to start on the database design part of
>> triage? For starters i have downloaded the postgresql database with GUI
>> interface from http://enterprisedb.com.
>>
>>
>> thanks,
>> Sai Mukund Sagar,
>> Vasavi College of Engg.
>> Hyderabad-500031.
>>
>>



Sai Mukund Sagar,
Vasavi College of Engg.
Hyderabad-500031.

[triage] Database Design

[SMS <muk...@gm...>]

Hi ,
Now that the unity prototype coding is complete and as far as the lift
deployment is concerned, i have deployed it .Yet there is still some error
though now i am able to see the Unity page and it works fine.Taking things
in triage ahead, when are we going to start on the database design part of
triage? For starters i have downloaded the postgresql database with GUI
interface from http://enterprisedb.com.


thanks,
Sai Mukund Sagar,
Vasavi College of Engg.
Hyderabad-500031.

[triage] (no subject)

[rajkumar g. <goe...@gm...>]

HI All,I was selected  for GonGtonG project and I've given GonGtonG project
as my final year project in the  college.Mukund and me also have completed a
small prototype of Unity.Because we had very minimal discussion about the
gongtong during the initial stages and the days are fast going by I request
to be reallocated to Triage project so that I could submit it as my Final
year project.I've already requested  about the change of the project in my
college and they've agreed .
Regards,
Rajkumar Goel
www.twitter.com/rajkumargoel
www.latestfever.blogspot.com

Re: [triage] Triage as final year project

[SMS <muk...@gm...>]

Hi Namita,
Yes I have already submitted Triage as my final year project at college.

thanks,

SMS

On Wed, Sep 30, 2009 at 2:37 AM, Namita Iyer <na...@tw...> wrote:

> Hi Mukund,
>
> Please confirm if you have formally submitted Triage as your final
> year project at college.
>
> thanks,
> Namita
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> twincling-triage mailing list
> twi...@li...
> https://lists.sourceforge.net/lists/listinfo/twincling-triage
>



-- 
Sai Mukund Sagar,
Vasavi College of Engg.
Hyderabad-500031.

[triage] Triage as final year project

[Namita I. <na...@tw...>]

Hi Mukund,

Please confirm if you have formally submitted Triage as your final 
year project at college.

thanks,
Namita

[triage] Lift Error

[SMS <muk...@gm...>]

Exception occured while processing /Unity

Message: java.lang.IllegalArgumentException: line 7 does not exist
	scala.io.Source.getLine(Source.scala:280)
	scala.io.Source.report(Source.scala:368)
	scala.io.Source.reportError(Source.scala:355)
	scala.io.Source.reportError(Source.scala:344)
	scala.xml.parsing.MarkupParser$class.reportSyntaxError(MarkupParser.scala:1113)
	net.liftweb.util.PCDataXmlParser.reportSyntaxError(PCDataMarkupParser.scala:91)
	scala.xml.parsing.MarkupParser$class.reportSyntaxError(MarkupParser.scala:1117)
	net.liftweb.util.PCDataXmlParser.reportSyntaxError(PCDataMarkupParser.scala:91)
	scala.xml.parsing.MarkupParser$class.document(MarkupParser.scala:186)
	net.liftweb.util.PCDataXmlParser.document(PCDataMarkupParser.scala:91)
	net.liftweb.util.PCDataXmlParser$.apply(PCDataMarkupParser.scala:102)
	net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1$$anonfun$apply$64.apply(LiftSession.scala:1096)
	net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1$$anonfun$apply$64.apply(LiftSession.scala:1096)
	net.liftweb.util.Full.flatMap(Box.scala:332)
	net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1.apply(LiftSession.scala:1096)
	net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1.apply(LiftSession.scala:1096)
	scala.Function1$$anonfun$andThen$1.apply(Function1.scala:48)
	scala.Stream.loop$2(Stream.scala:448)
	scala.Stream.flatMap(Stream.scala:456)
	scala.Stream.flatMap(Stream.scala:218)
	net.liftweb.util.ListHelpers$class.first(ListHelpers.scala:50)
	net.liftweb.util.Helpers$.first(Helpers.scala:29)
	net.liftweb.http.TemplateFinder$.findAnyTemplate(LiftSession.scala:1096)
	net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$findVisibleTemplate(LiftSession.scala:625)
	net.liftweb.http.LiftSession$$anonfun$7.apply(LiftSession.scala:461)
	net.liftweb.http.LiftSession$$anonfun$7.apply(LiftSession.scala:461)
	net.liftweb.util.EmptyBox.or(Box.scala:374)
	net.liftweb.http.LiftSession.processRequest(LiftSession.scala:461)
	net.liftweb.http.LiftServlet.net$liftweb$http$LiftServlet$$dispatchStatefulRequest(LiftServlet.scala:244)
	net.liftweb.http.LiftServlet$$anonfun$2.apply(LiftServlet.scala:176)
	net.liftweb.http.LiftServlet$$anonfun$2.apply(LiftServlet.scala:176)
	net.liftweb.http.S$.net$liftweb$http$S$$wrapQuery(S.scala:398)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1$$anonfun$apply$16.apply(S.scala:453)
	net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:372)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$doAround$1.apply(S.scala:373)
	net.liftweb.mapper.DB$$anon$1.net$liftweb$mapper$DB$$anon$$doWith(DB.scala:117)
	net.liftweb.mapper.DB$$anon$1$$anonfun$net$liftweb$mapper$DB$$anon$$doWith$1.apply(DB.scala:118)
	net.liftweb.mapper.DB$$anon$1$$anonfun$net$liftweb$mapper$DB$$anon$$doWith$1.apply(DB.scala:118)
	net.liftweb.mapper.DB$.use(DB.scala:320)
	net.liftweb.mapper.DB$$anon$1.net$liftweb$mapper$DB$$anon$$doWith(DB.scala:118)
	net.liftweb.mapper.DB$$anon$1.apply(DB.scala:124)
	net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:373)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1.apply(S.scala:451)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$.net$liftweb$http$S$$_nest2InnerInit(S.scala:450)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$19$$anonfun$apply$20$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24.apply(S.scala:471)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$19$$anonfun$apply$20$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23.apply(S.scala:470)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$19$$anonfun$apply$20$$anonfun$apply$21$$anonfun$apply$22.apply(S.scala:469)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$19$$anonfun$apply$20$$anonfun$apply$21.apply(S.scala:468)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$19$$anonfun$apply$20.apply(S.scala:467)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$19.apply(S.scala:466)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1.apply(S.scala:465)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$.net$liftweb$http$S$$_innerInit(S.scala:464)
	net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$27$$anonfun$apply$28$$anonfun$apply$29$$anonfun$apply$30.apply(S.scala:495)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$27$$anonfun$apply$28$$anonfun$apply$29.apply(S.scala:494)
	net.liftweb.http.RequestVarHandler$.apply(Vars.scala:191)
	net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$27$$anonfun$apply$28.apply(S.scala:493)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$27.apply(S.scala:492)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$$anonfun$_init$1.apply(S.scala:491)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.S$._init(S.scala:490)
	net.liftweb.http.S$.init(S.scala:334)
	net.liftweb.http.LiftServlet.doService(LiftServlet.scala:175)
	net.liftweb.http.LiftServlet$$anonfun$doIt$1$1.apply(LiftServlet.scala:104)
	net.liftweb.http.LiftServlet$$anonfun$doIt$1$1.apply(LiftServlet.scala:104)
	net.liftweb.util.TimeHelpers$class.calcTime(TimeHelpers.scala:241)
	net.liftweb.util.Helpers$.calcTime(Helpers.scala:29)
	net.liftweb.util.TimeHelpers$class.logTime(TimeHelpers.scala:250)
	net.liftweb.util.Helpers$.logTime(Helpers.scala:29)
	net.liftweb.http.LiftServlet.doIt$1(LiftServlet.scala:103)
	net.liftweb.http.LiftServlet.service(LiftServlet.scala:112)
	net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1$$anonfun$apply$24.apply(LiftServlet.scala:533)
	net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1$$anonfun$apply$24.apply(LiftServlet.scala:533)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.URLRewriter$.doWith(Req.scala:390)
	net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1.apply(LiftServlet.scala:532)
	net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1.apply(LiftServlet.scala:526)
	net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5$$anonfun$apply$6.apply(Vars.scala:197)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5.apply(Vars.scala:196)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4.apply(Vars.scala:195)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.RequestVarHandler$$anonfun$apply$3.apply(Vars.scala:194)
	net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	net.liftweb.http.RequestVarHandler$.apply(Vars.scala:193)
	net.liftweb.http.LiftFilterTrait$class.doFilter(LiftServlet.scala:525)
	net.liftweb.http.LiftFilter.doFilter(LiftServlet.scala:544)
	org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
	org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
	org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
	org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
	org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
	org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	org.mortbay.jetty.Server.handle(Server.java:326)
	org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
	org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
	org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
	org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
	org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
	org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

Re: [triage] TRIAGE MODULES

[SMS <muk...@gm...>]

Sure Saifi.

thanks,

SMS

On Fri, Sep 18, 2009 at 11:08 AM, Saifi Khan <sai...@tw...>wrote:

>
> >  -------Original Message-------
> >  From: SMS <muk...@gm...>
> >  Subject: [triage] TRIAGE MODULES
> >  Sent: 18 Sep '09 07:02
> >
> >  Hi All,
> >
> >  Triage consists of many modules. Each dealing with a functionality.
> >  This is the list of modules in Triage.
> >
> >
>
> Mukund, pls post the same content on the project forum on twincling.org
>
>
> thanks
> Saifi.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> twincling-triage mailing list
> twi...@li...
> https://lists.sourceforge.net/lists/listinfo/twincling-triage
>



-- 
Sai Mukund Sagar,
Vasavi College of Engg.
Hyderabad-500031.

Re: [triage] TRIAGE MODULES

[S. K. <sai...@tw...>]

>  -------Original Message-------
>  From: SMS <muk...@gm...>
>  Subject: [triage] TRIAGE MODULES
>  Sent: 18 Sep '09 07:02
>  
>  Hi All,
>  
>  Triage consists of many modules. Each dealing with a functionality.
>  This is the list of modules in Triage.
>  
>  

Mukund, pls post the same content on the project forum on twincling.org


thanks
Saifi.

Re: [triage] TRIAGE MODULES

[S. K. <sai...@tw...>]

>  -------Original Message-------
>  From: SMS <muk...@gm...>
>  Subject: [triage] TRIAGE MODULES
>  Sent: 18 Sep '09 07:02
>  
>  Hi All,
>  
>  Triage consists of many modules. Each dealing with a functionality.
>  This is the list of modules in Triage.
>  
>  
>   QA Analysis ,
>   Dashboard ,
>   Visualization ,
>   Project Metrics ,
>   Risk Analysis ,
>   Installer ,
>   Backup , Restore ,Upgrade ,
>   Configuration ,
>  
>   Role Based Access Control (RBAC) ,
>   Plug-in Framework ,
>   Admin (Triage Admin) ,
>   Theme ,
>   Components ,
>   Template ,
>  
>   Adapter ( bugzilla , mantisBT) ,
>   User ,
>   Workflow ,
>   Milestone ,
>   Timeline ,
>   Road Map ,
>  
>   iTriage ,
>   Triage Widgets ,
>   Registration ,
>   Project ,
>   Requirements ,
>   Ticket/Issue ,
>   Test Cases ,
>   Defects / Bugs ,
>  
>   Collaboration ( microblog , work group, mailing lists )So these make up
>  the list of modules in the Triage Project.
>  
>  
>  --
>  Sai Mukund Sagar,
>  Vasavi College of Engg.
>  Hyderabad-500031.
>  

Thanks Mukund for the list.

This will help with the database design work.

thanks
Saifi.

[triage] TRIAGE MODULES

[SMS <muk...@gm...>]

Hi All,

Triage consists of many modules. Each dealing with a functionality.
This is the list of modules in Triage.


   1. QA Analysis ,
   2. Dashboard ,
   3. Visualization ,
   4. Project Metrics ,
   5. Risk Analysis ,
   6. Installer ,
   7. Backup , Restore ,Upgrade ,
   8. Configuration ,
   9. Role Based Access Control (RBAC) ,
   10. Plug-in Framework ,
   11. Admin (Triage Admin) ,
   12. Theme ,
   13. Components ,
   14. Template ,
   15. Adapter ( bugzilla , mantisBT) ,
   16. User ,
   17. Workflow ,
   18. Milestone ,
   19. Timeline ,
   20. Road Map ,
   21. iTriage ,
   22. Triage Widgets ,
   23. Registration ,
   24. Project ,
   25. Requirements ,
   26. Ticket/Issue ,
   27. Test Cases ,
   28. Defects / Bugs ,
   29. Collaboration ( microblog , work group, mailing lists )

So these make up the list of modules in the Triage Project.




-- 
Sai Mukund Sagar,
Vasavi College of Engg.
Hyderabad-500031.

[triage] Println

[rajkumar g. <goe...@gm...>]

HI,
 object lists{
def main(args:Array[String]){
val nums=List(1,2,3,4,5,6,7,8,9,0)
val fruits=List("Apple","Banana","Cheekoo","Jack
Fruit","Grapes","Mango","Orange","Papaya")
println(nums)
println((nums.tail).tail)
println(fruits.head)
println(fruits.tail)
println(fruits)
}
}
HOW TO WRITE ALL PRINTLN 'S IN ONE LINE

i AM GETTING ERROR IF I WRITE "+" IN BETWEEN so how do we do that in scala

-- 
Regards,
Rajkumar Goel
www.twitter.com/rajkumargoel
www.latestfever.blogspot.com

[triage] Audit Trail

[Mukund D. <muk...@gm...>]

Hi All,

*Audit Trail*

Audit Trail is used to capture any event that falls through the
workflow.(Consider the case where a user registers at a website with fake id
then using Audit Trail we capture this event and block the
registration).Audit Trail is a component that overlaps between the Triage
and GongTong thus filling the significant gap between them.Auditor is the
admin for the Audit Trail component. So if there are any short comings or
problems that arise in a work flow the auditor checks it.

Here goes an example by saifi which illustrates the necessity of Audit Trail


 Here is an illustrative case:
. user visits the website
 . user registers on the site
 . user registration is blocked
 . administrator reviews the registration request
 . admin detects that the email address is actually spam.
 . admin deletes the user account.
 Now: . from the pov(point of view) of system, the given user 'abcxd' does
not exist.
. from the pov of auditor, a user with userid 'abcxd' indeed registered, but
was deleted.

The significant overlap here like in our case (Triage and GongTong) is
"audit trail" component !

the gaps in the above workflow

each of the steps enumerated above in the 'illustrative case' has some
fields associated.
 and some 'operation' associated.
 and some 'role' associated.
and some 'module' associate'
 so fieldType can be { field, operation, role, module }
 each auditLine is date-time-event-fieldType-value0-value1 (something along
these lines).
 Hence, the gap occurs when given a time and event for a fieldType, the
traceability between value0 and value1 is non-existent !

The same case can also be visualized for Triage and GongTong.Thus,Audit
Trail will act as a component to bridge the gap in the workflows of both the
project.

[triage] Triage Workflow

[Mukund D. <muk...@gm...>]

Hi Saifi,

In Triage Project From Installation to completion of a project).

Workflow- Its a sequence of operations/steps done to complete a logical
task.
All the steps that are to be followed to complete a project through Triage.

The *Main Workflow* should be like

1)The product is installed on a system and all the requirements are
assessed.Once it satisfies this Default installation is done.

2)The whole system is managed by a Triage Admin who creates and manages the
projects.

3)A Company or User can start a project where he should enter all required
details like specify time of start and end of the project/(s).

4)All this is validated by triage admin and the project/(s) is/are created.

5)An owner is assigned,who by default should be the one who initiates the
project.

6)People can join the team once they get registered and approved by the
owner of the project.

7)People working on the project can be given a tag of Project Managers who
have the right to make changes (As specified or granted by Project
Admin(Owner)) for example the time to complete the project.Add/rem members
of the team etc.,Divide work into components.etc.,

8)Every individual will be assigned task/tasks to accomplish with timeline
to complete the work.
If not done the reallocation can be done.

9)If any defects are found they are identified as bugs and they can be
solved voluntarily by anybody on the team.

10)Once the work done is assessed and the work of each team member is
integrated into respective Components

11)Then compnents are integrated to finally develop the product.Then, Unit
Test cases etc., are done.After this the Project is complete.

*Registration Workflow*

A user needs to have a registered username.so he needs to register
himself.So he has to go through the registration.And once completed he can
be assgned a project or he himself can create a project.

Well, this is my current uderstanding about the workflow in triage.

thanks,

SMS

[triage] Triage IRC summary(07-06-09)

[Mukund D. <muk...@gm...>]

Hi Team,

Team presnt at IRC :Saifi,Sreechand,Sai Mukund Sagar

Here is the summary of the IRC session

In today's IRC topics like the project admin, admin relations, delegation
model, rbac etc., have been discussed

*The Project Admin and Triage Admin*

The Triage Admin-->He/She manages the whole triage system which consists of
different projects.A Triage Admin plays no role within the project.
The Project Admin-->Each Project Admin takes care of his respective
project.Though a project Admin can handle more than one project.

If you consider tree like dependency,the actor who is at a higher level can
grant priveleges to actors at lower level(Root node is the highest
level).Consider a case where A proj Admin grants extra privileges to a
individual within the project for managing the project in a better way.Here
*"privilege escalation" *should be taken care of,i.e., No actor can grant
privileges more than what he enjoys.

*For better understanding of Triage Admin and Project Admin here goes an
example (quoted by saifi)*

1)The principal is the head of the college.so heads all the departments at
the same time does he decide for each dept what to do ?

2)The HoD deals with the profs/lects in a given dept.and a prof may also
teach across two or more departments too ;)


All the roles within the system would be configurable.The roles can be
differenitiated based on the operations they perform like

i)can manage
ii) can start
iii)can assign
iv) can deliver
v) can stop etc.,

Next about the blocks and components of Triage project

http://picasaweb.google.com/twincling/Triage#5344224248578990866
http://picasaweb.google.com/twincling/Triage#5344224250077228578
http://picasaweb.google.com/twincling/Triage#5344224253997153810

Each of this block  can be realized by implementing one or more plugins.(All
Plugins merged-->Triage)
The RBAC block refers to Role Based Access Control which has been
summarized.

For the next irc session please refer http://twincling.org/node/485


thanks,

SMS

Re: [triage] [stars] Triage photo notes

[Saifi K. <sai...@tw...>]

On Sat, 6 Jun 2009, Saifi Khan wrote:

> Hi all:
> 
> The Triage project "photo notes" to capture 
>  . design decisions
>  . drawings, 
>  . UI mockups, 
>  . workflows
> will evolve and be available at
> http://picasaweb.google.com/twincling/Triage
> 

Added three more closeups of the charts.
http://picasaweb.google.com/twincling/Triage#


thanks
Saifi.

[triage] Triage IRC summary(06-06-09)

[Mukund D. <muk...@gm...>]

Hi Team,

Team presnt at IRC :Saifi,Namita,Md.Sanaullah,Sreechand,Sai Mukund Sagar

Here is the summary of the IRC session

1)This month our main goal is to learn LIFT and Scala.(Keep Posting mails
regarding any doubts to twi...@ya...)
2)Our community hosting would be done at http://osuosl.org/services/hosting.
3)The workflow of the project has been discussed to a certain extent.
4)The Triage IRC time table has been changed.please have look at
http://www.twincling.org/node/485 *(Note :- we have IRC session at 0730 hrs
tomorrow)


*
*Why Scala and FP(Functional Programming)*

0. Scala is FP+OO1. FP is the future

2. those who won't switch loose out

3. OO is good for code organization

4. FP is excellent for components.

5. Scala is for components while Java is for objects

6. Scala builds on current enterprise investments in Application servers,
clustering, JVM etc.

7. the people who build the stuff first are also going to get some of the
best jobs that become available.

8. Scala is as fast/or more than Java. Java is 100 times faster than
Ruby/PERL/Python.

9.Scala scales linearly with increasing multi-core numbers. thats high
performance.

10. Finally, when an earthquake strikes the only people who survive are
those who move to the next safe location.


*Triage Specific* *Discussion*

Step 1:In triage a system will get installed in its default configuration
and is in maintenance mode once installed.
Step 2:Once installed "Triage Admin" i) creates a project
                                                      ii) names the project
                                                     iii) select the license
for project
                                                     iv) assigns owner to
the project
Step 3:Users are part of the project once they get registered i.e., they
visit the project site and apply for it if they wish to work for the
project.
Step 4:The admin may keep the details like allocation of work etc., to
individuals private or in incubation phase for sometime and then after
gettign organized (s)he may open it.

The IRC log has been posted already on stars mailing list.

thanks,

SMS.

[triage] Triage photo notes

[Saifi K. <sai...@tw...>]

Hi all:

The Triage project "photo notes" to capture 
 . design decisions
 . drawings, 
 . UI mockups, 
 . workflows
will evolve and be available at
http://picasaweb.google.com/twincling/Triage


thanks
Saifi.

[triage] Triage Project Notes

[SANAULLAH <san...@gm...>]

What is triage? Triage is a Work-flow oriented project engineering
management software.

Triage projects components are best understood in terms of the various
concepts discussed below:

Installer is used to verify the system requirements, satisfy the
dependencies, and define the default configuration for the
application. Any vulnerable configurations will be detected by the
installer.

Configuration: The default key-value properties of the system post installation.

Every time a new configuration is created the previous configuration
is backed up.

You can specify a Start Date and an End date for the project. The
timeline and the milestone for all the components of a particular
project will lie within the specified duration. This will have a
direct impact on the way the Validation logic works.

A component can be common across projects. In this case there will be
one "Owning" project and the rest would be "Using" projects. With this
logic wat it means is for this component the "Owning" project is an
"upstream" project for the "Using" project.

The customer raises an issue or opens a ticket. Customer Support
reviews the ticket and tries to reproduce the scenario. In case it is
unable to reproduce the scenario then it opens a defect for the QA
team.

The Dashboard has unique visualization, provides a graphical view of
the various projects, state of engineering, quality assessment, risk
analysis and degree of completeness.

Visualisation is done by using Charts- Progress bar to indicate the
project completion. To visualise wat is known in the project because
the project is done out of the wat is known. Known+unknown = 100%. %
of the project done is the % of known work done.

Adapters are application aware components written for migrating from
other point products to triage

Test cases written at System, Component and Unit level.

Triage widget- These are placed by the user on 3rd party websites.
Various projects metrics are highlighted.

iTriage- This is the page the user lands in when he logs in. This will
show the bird's eve view of the projects assigned to the user.

Risk Analysis involves predicting the risks and coming up ways to
tackle the same. This is estimated out of the list of unknowns, high
priority customer issues, blocker defects.

Workflow- Its a sequence of operations/steps done to complete a logical task.

Project is carefully a set of carefully designed activities tat
involves people, systems, collaboration, communication to achieve a
objective.

Requirement- Carefully written description of a criterian that the
work is expected to satisfy.

Specification- A specification is simply a plan for building something
that will satisfy the requirements

Admin- Administrator of the triage application.

Theme- Completely customizable theme as specified through CSS.

Template- Template for best practices.

Registration- Registration is used by the users for Sign up. ONly
registered users are eligible to apply and join the projects.

Project Metrics- These are the numeric parameters that help asses the
state of engineering for a project.

Application Quality Analysis Analytics- The most important thing is
the number of defects reported, average defect closure time (time
taken from the time it was allocated), defect allocation lag.


List of Cards:
Workflow
Ticket/Issue
Defect
Test Case
    - System Level
    - Component Level
    - Unit Level
MileStone
TimeLine
RoadMap
Dashboard
Component
Visualization
    - Charts
Installer
Configuration
Project
Requirements
Plug In Framework
Admin (Triage Admin)
User
RBAC- Role Based Access Control
Back Up, Restore and Upgrade
Adapter
    - bugZilla
    - mantisBT
    - trac
Registration
iTriage
Template
Theme
Triage Widget
Project Metrics
Risk Analysis
Application Quality Analysis Analytics
Collaboration
    - Mailing Lists
    - Work Group
    - Micro blog


Regards,

Mohamed Sanaulla
http://twitter.com/letmeknowupdate

[triage] Triage project

[Saifi K. <sai...@tw...>]

Hi Stars:

--
Triage project

Triage is a realtime work-flow oriented project engineering 
 management software.

 A team using Triage is able to 
 . define a project
 . organize project in components
 . specify requirements for the various components
 . work out test cases for the various requirements
 . identify milestones to define a roadmap
 . specify timelines for various milestones
 . manage defects and customer issues.
 . support defect linkage/push with upstreamm projects
 . incorporate best practices through templates

Within a single Triage installation, you can manage multiple 
projects without any issues or hassles.

For the senior leadership, Triage has a dashboard. The dashboard 
with unique visualization, provides a graphical view of the various 
projects, state of engineering, quality assessment, risk analysis 
and degree of completeness.

For existing projects, Triage provides application Adapters to import
 . bugzilla database
 . mantisBT database
 . trac database

Based on a plugin-based framework model, Triage is very flexible 
and configurable. Triage can be easily tailored to an organization 
or project's engineering requirements, best practice templates and 
branding requirements while hosting.

Triage provides plugins to integrate and support team communication 
using established Web 2.0 applications like blogs, twitter.com, 
laconi.ca etc. Based on new plugins, newer applications can be 
easily supported and existing features can be extended.

Triage provides an web-based administrator interface to manage the 
complete Triage application once it is hosted.

What is the technology ?
 Sun JRE 5/6
 Scala 2.7.4 (later 2.8.0)
 Lift 1.0 framework
 PostgreSql 8.3+
 plugin architecture
 ajax/jquery

What is the deployment model ?
 Dedicated hosting
 Amazon Elastic cloud (EC2) hosting.

What is the communication channel ?

 IRC
 #twincling on irc.freenode.net
 #twincling-triage
 
 mailing list
 https://lists.sourceforge.net/lists/listinfo/twincling-triage
 
 weekly status updates 
 
 everybody including mentors will post their status updates as
 a blog on twincling.org with the following tags
 . Open Source tag: project-name
 . Project tag    : status, update
 
--
Hope this helps.


thanks
Saifi.

Re: [triage] projects

[Saifi K. <sai...@tw...>]

On Tue, 14 Apr 2009, William Moses Jr. wrote:

> >From April 10 to May 14, all the projects are officially in 're-structure and re-setup' phase 
> 
> Hello Saifi, 
> Can I still go ahead and attempt to build the Twincling Web Installer?
> 

You are certainly very welcome to prototype the stuff !

This way, you get to learn the technology and the "intricacies" 
of software engineering (which are not apparent while reading a
sw-engg book or attending a lecture).


thanks
Saifi.

Re: [triage] projects

[W. M. J. <wi...@tw...>]

>From April 10 to May 14, all the projects are officially in 're-structure and re-setup' phase 

Hello Saifi, 
Can I still go ahead and attempt to build the Twincling Web Installer?

Re: [triage] projects

[Saifi K. <sai...@tw...>]

On Mon, 13 Apr 2009, swathi kota wrote:

> Hi Saifi,
> 
>   Installed Postgresql. Regarding the generation of sql scripts , do i need
> to write a php code which transfers the tables or do i need to generate
> mysql script and then change the syntax.
> 
> Thanks,
> Swathi.
> 

Hi Swathi:

You are welcome to do any investigation that you wish to do as part of
your personal study.

>From April 10 to May 14, all the projects are officially in
're-structure and re-setup' phase ! 

When, the projects start on May 15, 2009, that is a fresh start
on a clean slate ! One may see different team members, different
projects altogether or different focus area.


thanks
Saifi.

[triage] Installed postgre

[swathi k. <sw...@tw...>]

Hi Saifi,

  Installed Postgresql. Regarding the generation of sql scripts , do i need
to write a php code which transfers the tables or do i need to generate
mysql script and then change the syntax.


Thanks,
Swathi.

[triage] updates and Plan of action

[swathi k. <sw...@tw...>]

Hi Saifi,
    This is regarding my work so far on triage and my plan of action.


*Explored*: Worked with bugzilla by creating test products and accounts.
Understood the schema to some extent.
http://www.ravenbrook.com/project/p4dti/tool/cgi/

*Plan of action:*


   1. Draw ER diagrams for the schema.
   2. Generate mysql scripts for the 56 tables and then convert them to
   postgre.

Could you tell me if there are any tools other than visual schema to convert
the schema to ER diagrams.

Thanks,
Swathi.