[Apache Bloodhound] New user registration: matevzb
New user registration for user matevzb -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #255: Remove all minified javascript and stylesheets for next release
#255: Remove all minified javascript and stylesheets for next release +--- Reporter: gjm| Owner: gjm Type: defect | Status: accepted Priority: blocker| Milestone: Release 3 Component: dashboard |Version: Resolution: | Keywords: +--- Comment (by jdreimann): Would it make sense to move /doc/ out of /trunk/ ? -- Ticket URL: https://issues.apache.org/bloodhound/ticket/255#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
svn commit: r1408312 - /incubator/bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/jquery-1.7.1.min.js
Author: gjm Date: Mon Nov 12 14:58:12 2012 New Revision: 1408312 URL: http://svn.apache.org/viewvc?rev=1408312view=rev Log: removing redundant minified jquery - towards #255 Removed: incubator/bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/jquery-1.7.1.min.js
Re: [Apache Bloodhound] #255: Remove all minified javascript and stylesheets for next release
#255: Remove all minified javascript and stylesheets for next release
+---
Reporter: gjm| Owner: gjm
Type: defect | Status: accepted
Priority: blocker| Milestone: Release 3
Component: dashboard |Version:
Resolution: | Keywords:
+---
Comment (by gjm):
r1408312 removes
{{{bloodhound_theme/bhtheme/htdocs/js/jquery-1.7.1.min.js}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/255#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #255: Remove all minified javascript and stylesheets for next release
#255: Remove all minified javascript and stylesheets for next release +--- Reporter: gjm| Owner: gjm Type: defect | Status: accepted Priority: blocker| Milestone: Release 3 Component: dashboard |Version: Resolution: | Keywords: +--- Comment (by jdreimann): I have now removed all .min. files from the /doc/ area and updated all references to them to point to non-minified files with r1408385. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/255#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Proposals/BEP-0001 added
Page Proposals/BEP-0001 was added by olemis
Comment: Bloodhound workflow BEP . Essentially #194 rewritten with style.
Content:
---8--8--8--8--8--8--8--8
= BEP 1 : Bloodhound ticket workflow #overview
[[PageOutline]]
|| '''PEP''' || 1 ||
|| '''Title''' || Bloodhound ticket workflow ||
|| '''Version''' || '''TODO''' ||
|| '''Last-Modified''' || '''TODO''' ||
|| '''Author''' || The Bloodhound project ||
|| '''Status''' || Active ||
|| '''Type''' || Process ||
|| '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] ||
|| '''Created''' || '''TODO''' ||
|| '''Post-History''' || '''TODO''' ||
== Abstract #abstract
In the natural evolution of any software it is sometimes necessary to make
changes that modify its behaviour and fix problems identified by users. This
''BEP'' documents the recommended process that
[wiki:/Proposals#Bloodhoundmembers Bloodhound members] and contributors should
follow in order to work on tickets created in the
[http://issues.apache.org/bloodhound issue tracker] .
== Proposal #proposal
The workflow installed in the issue tracker is defined in [TracIni the
configuration file] . In the following picture you will see a graphical
representation.
{{{
#!Workflow width=600
}}}
=== Ticket states #workflow-states
- [=#state_new] **new** : All tickets will enter this state
immediately after they are created. In general it
represents tickets for which no active work is
been carried at the moment but everything is ready
to start with it right away.
- [=#state_assigned] **assigned** : Tickets will enter this state once
work on the target issue has been
started/continued and will remain that way until
work is suspended or ticket is ''closed''.
- [=#state_needinfo] **needinfo** : The state
for idle tickets until the community can get to an
agreement on a subject or ticket owner
can figure out how to continue solving target
issue.
- [=#state_review] **review** : There is a plausible
solution (e.g. a patch) provided by an
[wiki:/Proposals#Bloodhoundmembers external contributor] that is pending for
review by [wiki:/Proposals#Bloodhoundmembers Bloodhound members].
- [=#state_closed] **closed** : Represents the
ultimate state of the
ticket. At this point a resolution has been
given to the target issue.
=== Recommended practices #best-practices
Consider the following suggestions when working with tickets.
- People shouldn't assign tickets to themselves unless they
are planning to work on them in the near future - it's not a landgrab.
- Purposefully leave some low priority, easy issues untouched
to be tackled last within a given milestone. Label them with
`starter` keyword so as to add them to a section
on the BloodhoundContributing page for newcomers to pick up.
== Rationale #rationale
Default ticket workflow didn't work very well for us . At the beginning tickets
ended up being assigned for long periods of time, not really reflecting their
state properly. This was particularly true in the following situations :
- It was hard to identify tickets with patches
pending for review.
- Sometimes work made on tickets had to be suspended
until the community could get to an agreement
or ticket owner could consult external sources
in order to make an informed decision to move
forward. The only options at hand were `new`
and `accepted` so there was not enough exposure
for these tickets.
As a consequence it was hard for potential contributors to really know if a
ticket could be usefully looked at by them. It was also a trouble for
reviewers/committers to determine if there was something to do.
In order to improve the situation,
[attachment:ticket:194:opensource-workflow.png open source workflow] was
selected as a candidate to be installed. It was better but not accurate enough
, hence it was adapted to our needs until we obtained current workflow. The
details are documented in #194.
== Workflow maintenance #maintenance
Workflow setup and configuration tasks will be performed by
[wiki:/Proposals#Bloodhoundmembers members] granted with `TRAC_ADMIN`
permission.
Requests for workflow enhancements will be formulated by creating new tickets
with the following fields :
- **type** : `enhancement`
- **milestone** : `Unassigned`
- **component** : `siteadmin`
- **keywords** : include `bh_workflow`
Feel free to assign any other values to remaining fields.
This ''BEP'' is never meant to be completed. No extra effort will be needed to
keep it up to date since content will be generated by WikiMacros.
== Resources #resources
See TracWorkflow for details on using the ticket workflow system.
=== Workflow enhancement proposals #bh-worflow-tickets
[[TicketQuery(keywords~=bh_workflow, format=table, col=id|summary|status)]]
== References #references
1. [wiki:/Proposals BEP
Re: [Apache Bloodhound] #194: Examine workflow for Bloodhound site
#194: Examine workflow for Bloodhound site +- Reporter: gjm| Owner: gjm Type: task | Status: review Priority: major | Milestone: Unscheduled Component: siteadmin |Version: Resolution: | Keywords: bh_workflow +- Changes (by olemis): * milestone: = Unscheduled -- Ticket URL: https://issues.apache.org/bloodhound/ticket/194#comment:19 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Proposals/BEP-0001 modified
Page Proposals/BEP-0001 was changed by olemis Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001?action=diffversion=3 Revision 3 Comment: BEP-0001 milestone : Unassigned = Unscheduled Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0001 = --- Proposals/BEP-0001 (version: 2) +++ Proposals/BEP-0001 (version: 3) @@ -89,7 +89,7 @@ Requests for workflow enhancements will be formulated by creating new tickets with the following fields : - **type** : `enhancement` - - **milestone** : `Unassigned` + - **milestone** : `Unscheduled` - **component** : `siteadmin` - **keywords** : include `bh_workflow` ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0001' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/Index modified
Page Proposals/Index was changed by olemis Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/Index?action=diffversion=3 Revision 3 Comment: Numerical index. Separate section for BEP guidelines Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/Index = --- Proposals/Index (version: 2) +++ Proposals/Index (version: 3) @@ -1,4 +1,15 @@ + += Bloodhound Enhancement Proposals Index #index-intro + This page contains the index of all [wiki:/Proposals Bloodhound Enhancement Proposals], known as BEPs. ''BEP'' numbers once assigned are never changed. Proposal history is tracked in each wiki page. -[[TitleIndex(Proposals,format=group,min=3)]] +== Numerical Index #index-by-number + +[[TitleIndex(Proposals/BEP,format=group,min=3)]] + +== Resources #resources + +For further instructions and style guidelines to consider when writing proposals see + +[[TitleIndex(Proposals/Formats,format=group,min=3)]] ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/Index Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/Index' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/Index modified
Page Proposals/Index was changed by olemis Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/Index?action=diffversion=4 Revision 4 Comment: BEP index TOC Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/Index = --- Proposals/Index (version: 3) +++ Proposals/Index (version: 4) @@ -1,5 +1,7 @@ = Bloodhound Enhancement Proposals Index #index-intro + +[[PageOutline]] This page contains the index of all [wiki:/Proposals Bloodhound Enhancement Proposals], known as BEPs. ''BEP'' numbers once assigned are never changed. Proposal history is tracked in each wiki page. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/Index Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/Index' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0001 modified
Page Proposals/BEP-0001 was changed by olemis Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001?action=diffversion=4 Revision 4 Comment: BEP-0001 : Added accepted state . Correct description for assigned state Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0001 = --- Proposals/BEP-0001 (version: 3) +++ Proposals/BEP-0001 (version: 4) @@ -33,9 +33,13 @@ - [=#state_new] **new** : All tickets will enter this state immediately after they are created. In general it represents tickets for which no active work is -been carried at the moment but everything is ready -to start with it right away. - - [=#state_assigned] **assigned** : Tickets will enter this state once +been carried out at the moment but everything should be ready +for anybody to start with it right away. + - [=#state_assigned] **assigned** : Request for action on a ticket +sent to a particular user but no work started yet. +Everything should be ready for that user to start with it +right away. + - [=#state_accepted] **accepted** : Tickets will enter this state once work on the target issue has been started/continued and will remain that way until work is suspended or ticket is ''closed''. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0001' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0001 modified
Page Proposals/BEP-0001 was changed by olemis Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001?action=diffversion=5 Revision 5 Comment: BEP-0001 : Enhanced description for needinfo state Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0001 = --- Proposals/BEP-0001 (version: 4) +++ Proposals/BEP-0001 (version: 5) @@ -44,9 +44,9 @@ started/continued and will remain that way until work is suspended or ticket is ''closed''. - [=#state_needinfo] **needinfo** : The state -for idle tickets until the community can get to an +for idle tickets. They will remain in this state until the community can get to an agreement on a subject or ticket owner -can figure out how to continue solving target +can figure out how to continue working towards a definitive solution for target issue. - [=#state_review] **review** : There is a plausible solution (e.g. a patch) provided by an ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0001' page. If it was not you, please report to .
