OCS Roadmap - Revision history

Alec: Flip order

2013-04-29T17:49:01Z

Flip order

Alec at 23:58, 19 April 2012

2012-04-19T23:58:31Z

Jmacgreg at 19:38, 10 February 2010

2010-02-10T19:38:19Z

Admin at 19:40, 16 September 2009

2009-09-16T19:40:48Z

Jmacgreg: Protected "OCS Roadmap" [edit=sysop:move=sysop]

2009-03-11T06:32:38Z

Protected "OCS Roadmap" [edit=sysop:move=sysop]

Jmacgreg: /* Milestone 2.3 (Q2 2009) */

2009-02-16T23:55:43Z

‎Milestone 2.3 (Q2 2009)

Jmacgreg at 21:28, 16 February 2009

2009-02-16T21:28:44Z

Jmacgreg at 21:11, 16 February 2009

2009-02-16T21:11:32Z

Jmacgreg: OCS-Roadmap moved to OCS Roadmap

2009-02-16T20:58:32Z

OCS-Roadmap moved to OCS Roadmap

Jmacgreg: OCS moved to OCS-Roadmap: cleanup

2009-02-16T20:55:41Z

OCS moved to OCS-Roadmap: cleanup

@@ Line 5: / Line 5: @@
 While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.3.x bugfixes into the master branch; less so with 2.4 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Journal Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully.
-==Milestone 2.3.x ('''Ad-hoc scheduling''')==
+==Milestone 3.0 ('''Not yet scheduled''')==
-As with [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.3.x_.28Ad-hoc_scheduling.29 OJS 2.3.x], OCS 2.3.x releases will be made as necessary to correct security issues or as sufficient minor fixes accumulate to make a release worthwhile.
+OJS 3.0, described [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_3.0_.28Not_yet_scheduled.29 here], will reconcile the departure in coding style pioneered by OMP by bringing OJS back into line, incorporating new UI tools and back-end structures. Broadly speaking this will be a priority for OCS as well, though timelines and plans for OCS are currently less defined. Much of this work will attempt to blur the distinctions between the different applications, further decreasing the amount of distinct code per application and introducing greater flexibility in workflow within each application.
 ==Milestone 2.4 ('''Not yet scheduled''')==
@@ Line 13: / Line 15: @@
 PKP currently intends to consider release plans for OCS 2.4 from the master branch after the same has been completed for OJS 2.4. See [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.4_.28Q3_2012.29 OJS Milestone 2.4] for details. It is possible that PKP will opt to jump directly to considering OCS 3.0, described below.
-==Milestone 3.0 ('''Not yet scheduled''')==
+==Milestone 2.3.x ('''Ad-hoc scheduling''')==
-OJS 3.0, described [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_3.0_.28Not_yet_scheduled.29 here], will reconcile the departure in coding style pioneered by OMP by bringing OJS back into line, incorporating new UI tools and back-end structures. Broadly speaking this will be a priority for OCS as well, though timelines and plans for OCS are currently less defined. Much of this work will attempt to blur the distinctions between the different applications, further decreasing the amount of distinct code per application and introducing greater flexibility in workflow within each application.
+As with [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.3.x_.28Ad-hoc_scheduling.29 OJS 2.3.x], OCS 2.3.x releases will be made as necessary to correct security issues or as sufficient minor fixes accumulate to make a release worthwhile.
-−
-* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details on the proposed modularization of PKP applications.

@@ Line 1: / Line 1: @@
 =Development Roadmap=
-You will find the OCS development roadmap for 2009 below. Please note that these dates are not fixed. OCS development is currently following two development branches: a 'stable' 2.1.x line which includes mainly bugfixes and will be an easy upgrade for users of the current 2.1.1 release (and who do not need much in the way of new features); and a 'devel' 2.3 line, which includes large-scale changes in the underlying codebase as well as many new features. (OCS numbering will skip from 2.1 to 2.3 to be brought in line with the OJS numbering scheme, as they share a fair amount of the same code.)
+You will find the OCS development roadmap for 2012 below. Please note that these dates are not fixed. OCS development is currently following two development branches: a 'stable' 2.3.x line which includes mainly bugfixes and will be an easy upgrade; and a 'master' 2.4 line, which includes large-scale changes in the underlying codebase as well as many new features, but is not yet ready for production use.
-While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.1.x bugfixes into the devel branch; less so with 2.3 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Journal Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully.
+While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.3.x bugfixes into the master branch; less so with 2.4 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Journal Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully.
-==Milestone 2.1.2 ('''Q1 2009''')==
+==Milestone 2.3.x ('''Ad-hoc scheduling''')==
-This is a planned stability/bugfix release of the 2.1.x line, roughly scheduled for April 2009. Very few new features will be included with this release.
+As with [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.3.x_.28Ad-hoc_scheduling.29 OJS 2.3.x], OCS 2.3.x releases will be made as necessary to correct security issues or as sufficient minor fixes accumulate to make a release worthwhile.
-* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.1.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= All bug reports]
-==Milestone 2.3 ('''Q4 2009''')==
+==Milestone 2.4 ('''Not yet scheduled''')==
-OCS 2.3 is a substantial upgrade from the 2.1.x line, including many new enhancements as well as all relevant bug fixes against 2.1.x., and is loosely scheduled for release around June 2009. This will be the first OCS release that will make use of the new abstracted PKP WAL common codebase. The User Interface will remain largely the same as the 2.1.x line. You can view all bug reports by type:
+PKP currently intends to consider release plans for OCS 2.4 from the master branch after the same has been completed for OJS 2.4. See [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.4_.28Q3_2012.29 OJS Milestone 2.4] for details. It is possible that PKP will opt to jump directly to considering OCS 3.0, described below.
-* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= All bug reports]
-* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_severity=enhancement&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= Feature requests/enhancements]
-* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=PKP+Web+Application+Library&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= PKP WAL bug reports]
-==Milestone 2.3.1 ('''Q1 2010''')==
+==Milestone 3.0 ('''Not yet scheduled''')==
-This is a planned stability/bugfix release of the 2.3 line, roughly scheduled for March 2010. Very few new features will be included with this release. With this release, the 2.3 line will be considered stable, and the 2.2 line will reach its end of life except for critical and security bug fixes.
+OJS 3.0, described [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_3.0_.28Not_yet_scheduled.29 here], will reconcile the departure in coding style pioneered by OMP by bringing OJS back into line, incorporating new UI tools and back-end structures. Broadly speaking this will be a priority for OCS as well, though timelines and plans for OCS are currently less defined. Much of this work will attempt to blur the distinctions between the different applications, further decreasing the amount of distinct code per application and introducing greater flexibility in workflow within each application.
-−
-* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.3.1&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All bug reports]
-−
-==Milestone 3.0 ('''Not yet slated''')==
-−
-This proposed release will represent a large-scale revamping of the PKP codebase, including the completion of abstracting common code from all applications into the PKP WAL; modularization of the remaining OCS codebase (so that components can be mixed and matched as necessary); substantial and comprehensive User Interface refinements; and further overall code refinements. The release date is largely hypothetical at this point, and no bugs have yet been filed against 3.0.
 * See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details on the proposed modularization of PKP applications.

@@ Line 16: / Line 16: @@
 * [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_severity=enhancement&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= Feature requests/enhancements]
 * [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=PKP+Web+Application+Library&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= PKP WAL bug reports]
 ==Milestone 3.0 ('''Not yet slated''')==

@@ Line 10: / Line 10: @@
 * [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.1.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= All bug reports]
-==Milestone 2.3 ('''Q2 2009''')==
+==Milestone 2.3 ('''Q4 2009''')==
 OCS 2.3 is a substantial upgrade from the 2.1.x line, including many new enhancements as well as all relevant bug fixes against 2.1.x., and is loosely scheduled for release around June 2009. This will be the first OCS release that will make use of the new abstracted PKP WAL common codebase. The User Interface will remain largely the same as the 2.1.x line. You can view all bug reports by type:

@@ Line 15: / Line 15: @@
 * [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= All bug reports]
 * [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_severity=enhancement&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= Feature requests/enhancements]
 ==Milestone 3.0 ('''Not yet slated''')==

@@ Line 1: / Line 1: @@
 =Development Roadmap=
-==Milestone 3.0 ('''Current - Q4 2009''')==
+You will find the OCS development roadmap for 2009 below. Please note that these dates are not fixed. OCS development is currently following two development branches: a 'stable' 2.1.x line which includes mainly bugfixes and will be an easy upgrade for users of the current 2.1.1 release (and who do not need much in the way of new features); and a 'devel' 2.3 line, which includes large-scale changes in the underlying codebase as well as many new features. (OCS numbering will skip from 2.1 to 2.3 to be brought in line with the OJS numbering scheme, as they share a fair amount of the same code.)
-'''<big>PKP Framework</big>'''
+While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.1.x bugfixes into the devel branch; less so with 2.3 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Journal Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully.
-* Development of a common framework for all PKP software.
-* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details.
-==Milestone 2.3 ('''Current - Q4 2008''')==
+==Milestone 2.1.2 ('''Q1 2009''')==
-* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2572 Timeline refinements]
+This is a planned stability/bugfix release of the 2.1.x line, roughly scheduled for April 2009. Very few new features will be included with this release.
-* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2860 Registration refinements]
+* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Conference+Systems&version=2.1.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1= All bug reports]
-* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2919 Enable Session Types to be identified]
-* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3457 Title Browse list refinements]
+==Milestone 2.3 ('''Q2 2009''')==

← Older revision		Revision as of 21:11, 16 February 2009
Line 13:		Line 13:
	* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2919 Enable Session Types to be identified]		* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2919 Enable Session Types to be identified]
	* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3457 Title Browse list refinements]		* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3457 Title Browse list refinements]
−
−	~~==Proposed for Future Release==~~
−
−	~~===User Interface===~~
−
−	* UI refactoring, most likely congruent with the proposed common framework development. See [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2848 bug 2848] for one example, although this is a much larger issue than just buttons.
−
−	* On the conference timeline, it is possible to close author registrations while submissions are still open. That should remain possible, but some kind of warning prompt would be ideal: "Do you really want to close author registration before the submissions are closed? Y/N".
−
−	* Add support for full bilingualism - interface and content
−
−	* Reword "path" in setup (not an absolute path, but an abbreviation). Perhaps the abbreviation should just be used by default.
−
−	~~=== Email ===~~
−
−	* We need to provide some way to mass e-mail ACCEPTED authors only. Right now, the only option is to e-mail all authors, which becomes awkward about halfway through the management process of the conference (repeatedly needing to find and de-select the rejected authors).
−
−	* Add a "sent mail" email log for the CM.
−
−	* When a registrant pays, have the system generate an email receipt.
−
−	~~=== Workflow ===~~
−
−	* Ability for the Director to rapidly assign papers to reviewers. For example, from the list of papers, make it possible to check off a group of papers and press an "Assign to Reviewer" option, which would pull up a list of Reviewers. Select one, hit Go and that would be it.
−
−	* Incomplete submissions should not go to the "unassigned" queue.
−
−	* Support for panel submissions.
−
−	* Add a warning on the final stage of the submission process indicating that by clicking on the button the submission will be complete.
−
−	* Add flexibility to include multiple options for the type of presentation being proposed.
−
−	* Make Blind Reviews optional, allowing Conference Managers to decide whether or not to include author information in the Submission Metadata, visible to the Reviewer.
−
−	* Add flexibility to include more personal information from authors (e.g., title/rank/status of the individual, such as professor, student, professional, etc.)
−
−	* Add a "review-lite" workflow option that simplifies/reduces the peer-review aspects and allows conference directors to focus on using
−	~~OCS as an access, scheduling, and general logistical tool for their conference.~~
−
−	* Add a "collaborative review" workflow, where selected reviewers receive all submissions
−
−	~~=== Import/export ===~~
−
−	* Ability to export abstracts, user data, etc. into a tab delimited and/or XML format for manipulation outside of OCS.
−
−	* Export list of unpaid registrants.
−
−	~~=== Miscellaneous ===~~
−
−	* When a user logs in with NO role, some kind of useful message should be displayed. For example:
−
−	~~Would you like to:~~
−
−	~~[] Submit a proposal~~
−	~~[] Register as a conference reviewer~~
−	~~[] Register to attend the conference~~
−
−	~~This would help cut down on the many questions around this issue.~~
−
−	* Ability to set up as a single, one-off conference site
−
−	* Allow Conference Manager and Director role to be merged for a simpler option
−
−	* Add a budgeting module, which would allow conference managers to track conference expenses and generate cost reports.