You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
(9) |
Aug
(8) |
Sep
(31) |
Oct
(9) |
Nov
(7) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(5) |
Feb
|
Mar
(5) |
Apr
(9) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mike N. <mh...@us...> - 2004-08-16 16:37:44
|
Everyone, I think I have a new approach to tracker management that may be more palatable for the project members. Proposal: Significant subprojects will have a tracker created for them. This will allow subproject teams to create their own triage system. The teams can define Category, Group, Priority, and Canned Response options within their tracker. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: George B. <gbr...@lu...> - 2004-08-05 19:55:18
|
I'm thinking of creating some new modules for phpWS to provide features that schools need, and it seems to me that the work would be much facilitated by extending existing phpWS classes. I've done that before using the core item and manager classes, but would like also to consider extending classes defined in modules. For example, why not use the editing environment of PageMaster's PHPWS_Section class to store and edit mini news stories for a student newspaper module? I'm not clear, however, on how to make this work. Is it sufficient to require the mod/pagemaster/class/Section.php file and then to call the class functions, e.g., the constructor: $newsection = new PHPWS_Section::PHPWS_Section(); Is any other initialization required? Seems to me the appropriate tables had to have been installed in the database, for example, which is a boost process from installing pagemaster. I guess also one must check to see if the Section.php file exists. Is there some standard check to see if required modules are available? I seem to remember something like that from 'way back, but I've never used it. How does this work now? Any help appreciated! George ______________________________________ George Brackett, Principal George Brackett Associates 617 413 4316 / gbr...@lu... http://www.luceatlux.com/gba/ |
From: Mike N. <mh...@us...> - 2004-08-02 18:20:27
|
On Mon, 2004-08-02 at 07:54, Mike Noyes wrote: > Does anyone know of a good UML diagram program for reverse engineering > PHP code? Everyone, Has anyone tried AutoDia? http://droogs.org/autodia/ http://www.gnome.org/projects/dia/links.html -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-08-02 16:06:31
|
On Mon, 2004-08-02 at 07:54, Mike Noyes wrote: > Does anyone know of a good UML diagram program for reverse engineering > PHP code? Everyone, It looks like ArgoUML now supports PHP. I'm not sure if it can reverse engineer PHP code though. http://argouml.tigris.org/ -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-08-02 14:58:41
|
On Mon, 2004-08-02 at 07:54, Mike Noyes wrote: > Diazy looks interesting, but I don't think it can process PHP yet. > > http://diazy.sourceforge.net/ AutoGraf is interesting too, but it also lacks PHP support. http://autograf.sourceforge.net/ -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-08-02 14:49:00
|
Everyone, Does anyone know of a good UML diagram program for reverse engineering PHP code? Google string: "Unified Modeling Language"|uml (reverse|roundtrip ~engineer) php Diazy looks interesting, but I don't think it can process PHP yet. http://diazy.sourceforge.net/ -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-07-26 16:52:13
|
Everyone, I just placed a messages.po file in our repository. I will keep it in sync with the /phpwebsite094/locale/source.po file in the ASU repository. messages.po http://cvs.sourceforge.net/viewcvs.py/phpwebsite-comm/l10n/ Language localization people can start work on translations now. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-07-02 14:17:51
|
On Thu, 2004-07-01 at 10:15, Ulf Hallmann wrote: > would that mean that information-driven sites would have to stick on > the current version and remain un-updatable for good? Bummer. As I > said, I am running some sites like that. They work great - am willing > to show you, but I dont want to post the links across the whole list. Ulf, Can you point the list members to a document (see example link below) outlining your system? I'd like to see a formal proposal, patch (cvs unified diff), or prof-of-concept. Is it a true i18n solution or just l10n? Thanks. W3C Internationalization Activity http://www.w3.org/International/ Note: if you have a patch (cvs unified diff) we can host it at -comm. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Wendall C. <wen...@83...> - 2004-07-01 21:42:04
|
I have it installed on my laptop...I'll get on creating a theme right away. Wendall On Thu, 2004-07-01 at 14:12, Mike Noyes wrote: > Subject was: Re: [-comm-devel] Re: Please assign open problems to me > On Thu, 2004-07-01 at 11:10, Wendall Cada wrote: > > I'll help Mike get the wiki up and running so we can start building > > documentation and site docs as a group. > > Wendall, > Thanks for offering to help. > > I'd still like to use MediaWiki, but I'm not sure how well it will > coexist with phpWebSite in a single database. It looks like they > corrected the problem with php 4.1.2, so we can install on SF again. > > Have you looked into the theme/skin system yet? -- "Only the ideas that we really live have any value." --Hermann Hesse (Demian) |
From: Mike N. <mh...@us...> - 2004-07-01 21:17:22
|
On Thu, 2004-07-01 at 11:10, Wendall Cada wrote: > The method Mike is implementing will allow -comm be able to handle > multiple jobs. I think the biggest thing Mike needs at this point is > feedback. Wendall, Yes. I've been stuck on some of the finer details. We could even work them out as we go, but we need a system. The first thing is to get drafts created from the mess I posted earlier. > I know there are several of us admins capable of administering the > triage queue. We just need to communicate on who is doing so and when. Everyone, Are there any volunteers for this job? > With the number of projects now at -comm, it is time to just make the > thing work. Wendall, Agreed. > I for one wouldn't want anybody but Mike handling this as he knows the > SF.net system better than any of the phpWebSite developers. Let's just > keep giving constructive feedback and get things ironed out. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-07-01 21:08:24
|
Subject was: Re: [-comm-devel] Re: Please assign open problems to me On Thu, 2004-07-01 at 11:10, Wendall Cada wrote: > I'll help Mike get the wiki up and running so we can start building > documentation and site docs as a group. Wendall, Thanks for offering to help. I'd still like to use MediaWiki, but I'm not sure how well it will coexist with phpWebSite in a single database. It looks like they corrected the problem with php 4.1.2, so we can install on SF again. Have you looked into the theme/skin system yet? -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Wendall C. <wen...@to...> - 2004-07-01 18:10:44
|
+1 for the triage system. I don't want to see the tracker and task queues become a big mess. The biggest problem is that the sf.net system was originally designed for individual projects. The method Mike is implementing will allow -comm be able to handle multiple jobs. I think the biggest thing Mike needs at this point is feedback. I know there are several of us admins capable of administering the triage queue. We just need to communicate on who is doing so and when. With the number of projects now at -comm, it is time to just make the thing work. I for one wouldn't want anybody but Mike handling this as he knows the SF.net system better than any of the phpWebSite developers. Let's just keep giving constructive feedback and get things ironed out. I'll help Mike get the wiki up and running so we can start building documentation and site docs as a group. Wendall On Thu, 2004-07-01 at 11:02, Mike Noyes wrote: > On Thu, 2004-07-01 at 08:43, Tony Miller wrote: > > I thought that what I had asked wasn't unreasonable (it's a switch > > that's flipped, auto-assigning issues to the guy who wrote the > > module). There seems to be a level of complication and > > administration that I don't really believe is necessary. > > Tony, > It isn't unreasonable. I'll even capitulate on this, if the community > thinks the project can function without a triage system. I'm just > concerned the tracker and task queues will become an unmanageable mess > over time. This happened on LEAF, and I still haven't sorted the mess > out. It also happened to SF (Alexandria). Jacob Moorman was able to put > a triage system in place that corrected the problem. Take a look at > their queue for an example of what I'd like to see us implement. > > https://sourceforge.net/tracker/?group_id=1&atid=200001 > > > This is just my opinion, and I'm assuming this list is where we can > > voice our opinions. > > It is. Opinions are how consensus is achieved. It's often a messy > process, but the results are worth while. :-) > > > Why IS phpwebsite on SorceForge? It seems that the CVS tree is being > > hosted elsewhere. > > SF projects can make use of selected features. The phpWebSite ASU team > decided to make use of SF forums, trackers, and developers mailing list. > They desired local control of these resources at ASU: CVS repository, > website, and cvs notice list. phpWebSite Community Development was > founded to allow third parties a place to contribute to phpWebSite, as > access to the ASU cvs repository is restricted, etc. > > > I would really miss the tracker. It's one of the main reasons I joined > > the project on SF. > > I would also, but all the alternatives have features equivalent to the > ones provided by SF available. -- "Only the ideas that we really live have any value." --Hermann Hesse (Demian) |
From: Mike N. <mh...@us...> - 2004-07-01 17:58:20
|
On Thu, 2004-07-01 at 08:43, Tony Miller wrote: > I thought that what I had asked wasn't unreasonable (it's a switch > that's flipped, auto-assigning issues to the guy who wrote the > module). There seems to be a level of complication and > administration that I don't really believe is necessary. Tony, It isn't unreasonable. I'll even capitulate on this, if the community thinks the project can function without a triage system. I'm just concerned the tracker and task queues will become an unmanageable mess over time. This happened on LEAF, and I still haven't sorted the mess out. It also happened to SF (Alexandria). Jacob Moorman was able to put a triage system in place that corrected the problem. Take a look at their queue for an example of what I'd like to see us implement. https://sourceforge.net/tracker/?group_id=1&atid=200001 > This is just my opinion, and I'm assuming this list is where we can > voice our opinions. It is. Opinions are how consensus is achieved. It's often a messy process, but the results are worth while. :-) > Why IS phpwebsite on SorceForge? It seems that the CVS tree is being > hosted elsewhere. SF projects can make use of selected features. The phpWebSite ASU team decided to make use of SF forums, trackers, and developers mailing list. They desired local control of these resources at ASU: CVS repository, website, and cvs notice list. phpWebSite Community Development was founded to allow third parties a place to contribute to phpWebSite, as access to the ASU cvs repository is restricted, etc. > I would really miss the tracker. It's one of the main reasons I joined > the project on SF. I would also, but all the alternatives have features equivalent to the ones provided by SF available. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-07-01 17:40:17
|
On Wed, 2004-06-30 at 14:21, Eloi George wrote: > Mike Noyes wrote: > >So far my efforts have been poor to say the least. Sorry. > > > I believe in 'ya, Mike! Eloi, Thanks for the vote of confidence. :-) > phpws-comm is a needed resource. It's only going to happen if we all > participate. Agreed. > However, I think that SF is not the place to host it. SF's structure > & policies are based on hosting various development teams in a central > repository. phpws-comm's (correct me if I'm wrong) purpose is to do > the same thing limited to a certain theme (phpWebsite). Essentially > we're hosting SF *on* SF! Actually, it is possible to host a project like ours on SF, it just requires additional administrative work. Example: fink, leaf, etc. > Mike, have you given any thought to hosting phpws-comm on the Appstate > servers or on phpwebsitemanual? We'd lose tracker functionality, but > except for forum-based moderators I think that phpwsbb make a wonderful > substitution. It is a possibility, but my usefulness would cease. My only redeeming values are related to my knowledge of the SF services, structure, and staff. Possible alternatives: savannah.gnu.org, gforge.org, www.egroupware.org Note: hosting becomes an issue with gforge and egroupware. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Tony M. <cl...@us...> - 2004-07-01 15:43:44
|
On Wed, 30 Jun 2004, Eloi George wrote: > Mike Noyes wrote: > > >So far my efforts have been poor to say the least. Sorry. > > > I believe in 'ya, Mike! > > Tony. Although I'm not one to talk because I release my module on both > SF and my own site, I do have to say that Mike *is* trying his level > best to administrate phpws-comm while having to deal with his real job & > that wicked cool scar he's sportin' now. That's cool. And I don't mean to criticize (yeah, I do :)), but I thought that what I had asked wasn't unreasonable (it's a switch that's flipped, auto-assigning issues to the guy who wrote the module). There seems to be a level of complication and administration that I don't really believe is necessary. This is just my opinion, and I'm assuming this list is where we can voice our opinions. > phpws-comm is a needed resource. It's only going to happen if we all > participate. However, I think that SF is not the place to host it. > SF's structure & policies are based on hosting various development teams > in a central repository. phpws-comm's (correct me if I'm wrong) purpose > is to do the same thing limited to a certain theme (phpWebsite). > Essentially we're hosting SF *on* SF! Why IS phpwebsite on SorceForge? It seems that the CVS tree is being hosted elsewhere. > Mike, have you given any thought to hosting phpws-comm on the Appstate > servers or on phpwebsitemanual? We'd lose tracker functionality, but > except for forum-based moderators I think that phpwsbb make a wonderful > substitution. I would really miss the tracker. It's one of the main reasons I joined the project on SF. -- Hometown Enterprises Internet Services Professional, affordable web design and hosting. http://www.hteis.com/ |
From: Eloi G. <el...@re...> - 2004-06-30 22:14:50
|
Mike Noyes wrote: >So far my efforts have been poor to say the least. Sorry. > I believe in 'ya, Mike! Tony. Although I'm not one to talk because I release my module on both SF and my own site, I do have to say that Mike *is* trying his level best to administrate phpws-comm while having to deal with his real job & that wicked cool scar he's sportin' now. phpws-comm is a needed resource. It's only going to happen if we all participate. However, I think that SF is not the place to host it. SF's structure & policies are based on hosting various development teams in a central repository. phpws-comm's (correct me if I'm wrong) purpose is to do the same thing limited to a certain theme (phpWebsite). Essentially we're hosting SF *on* SF! Mike, have you given any thought to hosting phpws-comm on the Appstate servers or on phpwebsitemanual? We'd lose tracker functionality, but except for forum-based moderators I think that phpwsbb make a wonderful substitution. *______________________________* |
From: Mike N. <mh...@us...> - 2004-06-30 21:10:40
|
Everyone, Here is what I have outlined for our triage system. It's a disjointed mess, so bear with me. ______ Some of the Subject and other initial triage (not complete) is visible in our SR queue. ____ http://cvs.sourceforge.net/viewcvs.py/phpwebsite-comm/documents/docmanager/en/ phpwebsite-comm/cvs/documents/docmanager/en Project Member Application <-- SR queue Continued Participation Check <-- administrative task quarterly Support Requests Priorities: 9 - Project member requests that require SF staff intervention 8 - Project member requests that require project admin intervention 7 - Project Member Applications 6 - Second level support 5 - First level support 3 - Later, Postponed, or Remind 1 - Duplicate, Invalid, Out of Date, Rejected, Wont Fix, Works For Me Groups: Administrative - Requests made by project members First Level Support - user support by any project member Second Level Support - direct support from project member that created the content in question. RFEs should be submitted in our Support Request tracker. They will then be processed by one of our project admins, and moved to our _private_ RFE tracker. Once a project member agrees to work on the RFE, a public Task will be opened for group coordination. Tasks: Feature Requests https://sourceforge.net/pm/task.php?group_project_id=30312&gr oup_id=81360&func=browse You can track this process using our auto mailing list. phpwebsite-comm-auto https://sourceforge.net/mail/?group_id=81360 ____ Support Request: Submit New Project Member Application Module Contribution Theme Contribution Modules tracker: The Modules tracker hosts one-time module contributions from the community. In addition, it hosts module contributions from people who don't wish to join phpwebsite-comm. All project member modules are hosted in our CVS repository and published using the File Release System. Themes tracker: The Themes tracker hosts one-time theme contributions from the community. In addition, it hosts theme contributions from people who don't wish to join phpwebsite-comm. All project member themes are hosted in our CVS repository and published using the File Release System. ____ LEAF Bugs: This tracker is visible to project members only. All tracker artifacts shall initiate in our support request tracker. Triage of new support requests will be performed. If the tracker artifact is a bug, it will be moved here and processed by the assigned technician. LEAF Support Requests: Creation of all new tracker data types (bugs, contributions, feature requests, patches, support requests) shall occur here. Triage (data type, category, assignment, summary, category, group, etc.) of new support request trackers will be performed. LEAF Support Requests Submit New: Please read "How do I request help?" before submitting a support request. Note: SourceForge Patch Manager file attachments must be > 20 bytes and < 256000 bytes in length. If your contribution is outside of this range, please provide a download location for your content. LEAF Patches: This tracker is visible to project members only. All tracker artifacts shall initiate in our support request tracker. Triage of new support requests will be performed. If the tracker artifact is a patch (unified diff), it will be moved here and processed by the assigned technician. LEAF Feature Requests: This tracker is visible to project members only. All tracker artifacts shall initiate in our support request tracker. Triage of new support requests will be performed. If the tracker artifact is a feature request (RFE), it will be moved here. Any project member may accept responsibility for the RFE by posting a message to our developer's mailing list. A project admin will then assign the RFE to the project member and close the RFE. The project admin will then create a project task referencing the RFE, so a project member team can be generated. The project member accepting responsibility for the RFE will be the task lead. ____ 00. LEAF SourceForge Site Answers https://sourceforge.net/docman/?group_id=13751 -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-06-30 19:26:17
|
On Mon, 2004-06-28 at 12:44, Tony Miller wrote: > On Mon, 28 Jun 2004, Mike Noyes wrote: > > I haven't completed the project policy documents on SR/tracker triage. I > > feel that auto assigning them at this time would be a mistake. > > Why is this? Is there anyone else who should be handling my bug > processing than me? Tony, Of course your bug's should be assigned to you. That's not the issue. The issue is a tracker may be given a bug status by a submitter erroneously. This is one of many possible mistakes a submitters can and do make daily. I'm trying to save you and the other developers time and effort required to respond to erroneous tracker artifacts. So far my efforts have been poor to say the least. Sorry. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-06-30 19:19:35
|
On Wed, 2004-06-30 at 11:03, Tony Miller wrote: > When I signed up for the project, I think I was confused about what it > was all about. I was under the impressions that this project was a > place to centrally locate individual projects to all corroberation if > it was wanted. Tony, You were not mistaken. I'm trying to setup a tracker/task system that multiple project members can utilize. I'm not there yet unfortunately. Also, my accident set back progress on this task considerably. > What it appears to be now is a centralized administration (who doesn't > seem to have time to administrate) has taken control of my module and > will decide if functionality is warranted and what the priority is, > and if bugs are legitimate and who they are assigned to. I'm not trying to decide anything for you. Your modules are under your control. I've never made a commit to your code. I'm only trying to figure out a sane way to coordinate all of these projects in the tracker/task managers available to us. Note: all trackers/tasks are posted to our phpwebsite-comm-auto list for review by everyone. https://sourceforge.net/mail/?group_id=81360 > Rather than helping my development efforts, this model seems to be > hindering it. I released an *emergency* news item outlining a bad bug > in my code, and the bug wasn't even listed in the news. I'm sorry if anything I've done or failed to do has caused you any hardship. It was not my intent. If at any time a majority of the project members wish me to step aside I will. I only serve while I further the best interests of our project. Unfortunately, the SF staff has news item release restricted to project admins at this time. I'm going to request a project user permission similar to release tech for news. > Have I completely misunderstood things? My intent yes. However, you may be correct in implementation. I'll leave that judgment to others. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Tony M. <cl...@us...> - 2004-06-30 18:04:01
|
When I signed up for the project, I think I was confused about what it was all about. I was under the impressions that this project was a place to centrally locate individual projects to all corroberation if it was wanted. What it appears to be now is a centralized administration (who doesn't seem to have time to administrate) has taken control of my module and will decide if functionality is warranted and what the priority is, and if bugs are legitimate and who they are assigned to. Rather than helping my development efforts, this model seems to be hindering it. I released an *emergency* news item outlining a bad bug in my code, and the bug wasn't even listed in the news. Have I completely misunderstood things? Thanks, -Tony -- Hometown Enterprises Internet Services Professional, affordable web design and hosting. http://www.hteis.com/ |
From: Mike N. <mh...@us...> - 2004-06-30 17:46:22
|
On Wed, 2004-06-30 at 10:05, Ulf Hallmann wrote: > My basic motivation is that I am running a bunch of web sites based on > phpws and that I would like to get my custom code supported. Well - > you might say: That's what we all want. Ulf, This is why the phpwebsite-comm project was started. It provides a place for community members to work on their ideas. It also provides a place for the ASU team to review content for inclusion in phpwebsite releases. > Multi-Language-Capability. Most of the current functionality in phpwebsite is l10n. The underlying support for i18n isn't implemented yet. i18n requires underlying structure support from database, web server, php code, xhtml, and css to function properly. > > First, I think that things like > http://sourceforge.net/tracker/?func=detail&aid=958502&group_id=15539&atid=315539 > http://sourceforge.net/tracker/?func=detail&aid=942393&group_id=15539&atid=315539 > http://sourceforge.net/tracker/?func=detail&aid=942365&group_id=15539&atid=315539 > should make it into the supported code of related core mods. Secondly, > I think that there should be a recommendation that phpws mods should > be tested regarding their lang mod integratability, ideally related > code would be already shipped with the mods and could be activated by > a flag. I am offering to help coordinating this effort and to provide > sort of I18N feedback to mod developers. If I knew who they are .... > > ... - which brings me to the third activity I'd like to initiate: A > more structured family of web sites where information like this can > easily be found by the regular user. I think I am an experienced web > user, but I often found myself lost in the large world of > phpws-support-sites. I'm going to setup a wiki (mediawiki) for phpwebsite-comm. I hope everyone can contribute to the knowledge base. > > I have been talking to Kenneth Poulsen about this (so far with no > success - maybe my baby break is the reason). A key benefit is that > this effort can leverage the multi-language activities that I > described above: By providing one multi-lingual core site that uses > great phpws features like branches etc. (1) to integrate other > supported sites and (2) to show everybody out there the great things > that can be done with a system that deserves to be the number one php > framework in the world. With your assistance we can work on this goal at phpwebsite-comm. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Tony M. <to...@ht...> - 2004-06-28 19:44:56
|
On Mon, 28 Jun 2004, Mike Noyes wrote: > On Mon, 2004-06-28 at 11:24, Tony Miller wrote: > > Could you please assign the open problems for quotes and > > mailto to me. Also, would it be possible to set those > > categories to automatically assign to me so that I can change > > priorities and close them. > > Tony, > I haven't completed the project policy documents on SR/tracker triage. I > feel that auto assigning them at this time would be a mistake. Why is this? Is there anyone else who should be handling my bug processing than me? > BTW, please use the devel mailing list for these messages. Ok. -Tony -- Hometown Enterprises Internet Services Professional, affordable web design and hosting. http://www.hteis.com/ |
From: Mike N. <mh...@us...> - 2004-06-28 19:10:49
|
On Mon, 2004-06-28 at 11:24, Tony Miller wrote: > Could you please assign the open problems for quotes and > mailto to me. Also, would it be possible to set those > categories to automatically assign to me so that I can change > priorities and close them. Tony, I haven't completed the project policy documents on SR/tracker triage. I feel that auto assigning them at this time would be a mistake. BTW, please use the devel mailing list for these messages. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-06-11 18:07:17
|
Everyone, It seems many of you are confused by my handling (triage) of tracker/task artifacts. This is my fault, I should have completed our project policy documents long ago. :-( Here is a quick overview. If you have questions or comments, please post them. Thanks. ---- 1.4 Trackers and Tasks ---- All tracker items (SR, RFE, Bugs, etc.) are created in our SR queue. They then go through triage, and are moved to the appropriate queue (data type). SR: Proper category determined; then group, assignment, and priority set. Bugs: Initiate in SR queue, and are assigned to responsible party when moved here. RFE: Submitted in our Support Request tracker. They will then be processed by one of our project admins, and moved to our _private_ RFE tracker. Once a project member agrees to work on the RFE, a public Task will be opened for group coordination. 1.4 Trackers and Tasks (draft broken - see cvs) https://sourceforge.net/docman/display_doc.php?docid=17112&group_id=81360 -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
From: Mike N. <mh...@us...> - 2004-06-11 15:50:00
|
Everyone, I'll try to finish creating our project policy documents in the near future. If you are releasing content (module, theme, l10n, etc.) in the SF FRS, please read the project policy document below and SF SiteDoc F2. Once that is done, I'll grant you release technician status. I'll even walk you through the SF FRS process on irc.freenode.net #phpwebsite. 1.3 File Release System (FRS) https://sourceforge.net/docman/display_doc.php?docid=17111&group_id=81360 -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |