PostNuke

Site search

Search results

Number of hits: 8

NOC up and running again   (News)

NOC is available again 24h/7 but that it's also really fast. Developers should also notice that the SVN is now much faster, too.

Enjoy it and give Drak a small (or bigger) donation for his expenses.

Generated on June 8, 2007.

Ongoing Problem with the NOC   (News)

We are upgrading the NOC server to a dual opteron, 4GB with 3 x 73GB SCSI drives using LSI's MegaRAID 320-1 controller. The cost of the hardware is approximately $3500. We would like to encourage all users to make a small donation to the PostNuke Server Fund here.

Generated on May 31, 2007.

PostNuke, Licenses, Commercialism....   (News)

built with PostNuke - for many sites it's obvious, for others not so obvious because there are some great theme designs out there.

As it stands, such popularity has also attracted many third-party developers to PostNuke, contributing blocks, modules and themes. While the spirit of free (as in 'free beer') software reigns for many contributors of such add-ons, a small community of commercial developers has also sprung up around our favorite CMS - and that's where some of the points of contention seem to come from.

Notably, some of the commercial developers are interested in providing their products in the form of binary-only (protected, and without source) form, in order to protect their commercial interest. These modules are *not* GPL (by virtue of not making their source code available). A veritable outcry has happened, albeit only by a very few, decrying what they claim amounts to heresy.

There are several issues at hand here, all of which we want to address, hopefully to the satisfaction of most, if not all:

- Commercial Products : It has always been our opinion that commercial ventures are encouraged, as they will invariably help strengthen the framework of PostNuke, and in turn help the community grow. Furthermore, commercial ventures will help PostNuke gain additional 'legitimate' recognition, as a serious tool in the field of business, or within the enterprise environment.

It is certainly the right of a developer to choose the way they want to distribute their software and it is your right to place a value on their time and effort, if you so choose. And unlike those few programmers that are independently wealthy, things like rent, food, and car payments don't get made by trading code (at least, not yet).

- 'All-Software-Must-Be-Free' Mentality - While it is certainly nice to be able to freely benefit from another's efforts, the basic reality is there is also (in our opinion) a lot of freeloading in that mindset. The purpose behind free software is to be able to freely trade with other programmers, who you then contribute code to - this worked in the old days within tightly knit programmer communities, but breaks apart as communities grow and more and more users join who have a variety of skills sets. Which means many aren't contributing code, but are looking for tools and resources. However, their contributions can be other valuable things like documentation and support, they can also contribute compensation in the forms of donations, postcards, or the ever popular universal currency, beer. As such, we believe free software is nice (and we will always appreciate anyone contributing generously), but likewise, shareware, donationware, and commercial software have a place that should be respected.

- Open Source Software - There's a big confusion over 'open source' and 'free', as there's a segment of the community that firmly believes if it's open source, it *must* be free. This certainly is not the case, as even the GPL specifies quite clearly products licensed under the GPL can be commercialized. In fact, it's encouraged. The key with the GPL license is only the source code has to be freely and easily accessible. This is both a benefit, but also a liablity for commercial products. On one hand, by making their code available, the community is able to contribute fixes and enhancements back to the commercial vendor - this has benefitted such diverse companies as linksys, TiVO, Apple and RedHat. Likewise, the availability of the source code also stands the danger of making proprietary
technology available to competitors - which is why many other commercial vendors sometimes pick different licenses allowing them to protect part of their technologies.

Still, if something is GPL, it stays GPL - that's why PostNuke will *ALWAYS* remain GPL licensed. There's many reasons why this is so, but the best is we know it is in the best interest of the project, as well as the community.

- Close-Source Contributions - this is the sticking point, wherein developers use the PostNuke framework, and contribute a module or add-on, that does not include the source code, and is distributed in a binary-only manner. Is this terrible? Is this evil? Is this the end of civilization as we know it? Of course, not.

Is it a violation of the GPL? The way we see it, it isn't (if done right - meaning no re-use of GPL code), but most of all, wether it is, or it isn't, IT IS NOT POSTNUKE'S RESPONSIBLITY! Why? Simple, because we cannot control third-party developers and a third-party product does not alter, or affect the copyright, trademark, or development process of the PostNuke Project. The few such products we have seen that fall into this category, target niche or vertical markets - thus, nothing PostNuke depends on.

The final decision regarding any such products or add-ons lies with YOU, the PostNuke community, as a commercial product will only be viable if it is being purchased. If you do not like how a vendor packages their products, if you do not like the way they sell them, if you do not like the prices, or the license - DO NOT BUY THEIR PRODUCTS! You may even take an additional step, and send them a polite letter as to why you will not be a customer, maybe if they get enough of these types of letters, it may convince them to alter their business model.

Finally, what kind of commercial products do we like, or rather, which contributors and developers are doing it 'right'? Two examples come to our minds right off the bat - AutoThemes, and Webvida.

With AutoTheme Shawn has created a nice theme utility with AutoTheme - not only making it easy to design themes, but also facilitating portability of themes among various compatible CMSs. While the 'pro' version of AutoTheme is a commercial product, Shawn makes a free version, AutoTheme Lite, available to anyone who needs it. As such, he gives his customer the option of what they want to use, and how they want to support him. The business model seems to be working quite well.

Webvida's Lobos provides themes for PostNuke, via AutoTheme. The themes seem well-designed, and affordably priced. In addition, many themes are provided at no charge, with new themes being added frequently. Also quite a bit of additional support and contributions in the form of tutorials are being provided by both Shawn and Lobos.

Lastly, both appear to be very active in the community, and provide support to the community, as well as to their users. Undoubtedly, there's value in what they provide, and this is commercialization, done right, in our opinion.

The final decision, as we stated above, on all of this, lies with the PostNuke community, as it is up to you to decide which vendors to support, and which not to - PostNukian Darwinism, so to speak - regardless of what any of us has to say, and certainly regardless of what any activists might feel about these issues.

Finally, to make sure we are clear on this issue, we encourage module developers and theme designers to contribute free and open source software to the community but we have no problem with them offering their products and services to the community as described in http://www.gnu.org/philosophy/selling.html

Since it's not yet legally proven it might be even permissible to release addons under a non-compatible GNU/GPL license providing the addons are not derivatives of existing GPL work. While we prefer to take a 'wait and see' attitude regarding such non-free add-ons, should you feel strongly enough about it, we encourage you to take matters into your own hands, and file a precedent setting lawsuit to prove this matter once and for all. We'll check in with you in a couple of years, okay? (Seriously, the effort of filing such a suit, or even being concerned over such situations is not worth expending - vote with your wallet.)

We hope this clears up some things, at least what our opinions are on these issues - and that's what they are, opinions. None of these are legally binding, or even legally proven, and should not be taken as such. We're not lawyers, and we don't want to be, either.

Generated on March 8, 2004.

Interview: Franky Chestnut, pnConcept.com   (News)

Hacks
dWl Mod Suite - This was for pn0.713, it was inspired from modifications that were done on the Downloads and Web Links modules at phpNuke. There is an All Page and that would be the only real important thing about this one. It was one of my first hacking I made. And to think of it, I still use the all page on my site [demo] but I think that is all that is left of the modifications. Also in this hack, I made it so there is a listbox with the title instead of just a field when you wanted to modify a link or a download. Little things like that. People should not use it today... all files comes from pn0.713.

pnMailUserHTMLHack - Another modification of the pn0.714 Mail User mod. All it did was to give the choice to send an email to a user in text or in html.

pncUserHack - None the least, this is my most popular work. It began with only the possibility to choose the password you want when registering and today, you can add dynamic fields, list, checkbox, define required fields, moderate registration and so on. Lots of options with the mail because for a time, the goal was to give admin the possibility to use PostNuke on hosting without mail function. But as users were asking more and more... it became what it is today.

pncUserHack was made with pn0.723 so I do not recommend it for newer version today. The future is unknown for this one, it depends on many things.

Blocks
Block Your_Avatar - My first block. It shows the avatar from your profile and a list box to change it directly on the block. Today, this one makes me laugh.

pncPaypalContribute - A pnAPI block that shows a Paypal button for donations. The email and currency can be choose in the administration for this block.

Mods
FeedBack- This was my first module and it still work although I think it was made for the pn0.6x or pn0.71x series. I took the Recommend_Us module and made it so it sends an email to the admin and it was my first experience. I saw later 2 or 3 modules that had the same name and we're doing the exact same thing. I thought it was funny but it was for everyone an easy way to start I guess.

pnUser_Points 0.22X - This one will disapear and I'll be glad because it never quite fully worked well. Not that it is a bad module but it doesn't work very well when your database becomes medium or large. The way it was written, it was using so much ressources that most of the time, the module couldn't update itself like it was supposed to do. What I did to put the 'x' after the 0.22 is that there was no administration in the original one. So you had to change the configuration directly in the files. And for me, I thought that it wasn't very..... actual. So I made the administration for the configuration and I added the possibility to clean the table where data was inserted. I also made the initialisation so people didn't had to insert the table by hands anymore.
I remember that I didn't want this one to go out with my name on it but since I didn't had any answer from the original authors when I finished it, I release it as it was. And people kept the association and came to me for the support and the future version.

Next version will make this one completly obsolete. 100% pnAPI, much less ressources, Groups points and Archives.

pncPopMessages - That one is a copy of the original Admin_Message but with a block include that would pop a message. I made a copy because I want to separate the original Admin messages from the messages that would pop.

pncGroups - I made this one because I didn't want to add manually users that would help us on PostNuke-France.org on various things. Documentation, support or even administrate a part of the site. So the module is giving the hability to the users to register for a group with all the permission fuss. You also can make a group open or close, define how many users can register for a particular group and so on. 2 blocks were included, one to show groups information and the other, the list of users in a particular group.

pncSimpleStats and pncSimpleStats Xantia - These are my last ones. While working on the pncUserPoints and discovering that ressources may not be a problem like the old User_Points was, I made this little Stats module with some some functions that were for the pncUP. For each category (news, comments, reviews and xforum), it shows a page with the list of users and the amount they proposed or wrote. No database, always getting the most recent count.
The Xantia version was my way of practicing with the new pnRender Engine and to give the result to the users. It is templated.

Upcoming
pncPaypalMod - Just my personal Paypal mod that won't do a zillion thing. The pncPaypalContribute will be moved to this mod. The goal is to make a simple mod that will show the list of contributors but won't have many functionality. I know there is probably 10 out there but I'm a programmer and I like to create my own. I just want something basic. I have a working version under a desk somewhere but never had the time to finish it. And.......... it will be free ;-) (No pun intended ha ha ha !)

All other upcoming mods are reactualisation, pnAPIsation and for some, templated of the existing ones : pncUserPoints, pncGroups, pncPopMessages, etc...

I also made the decision to concentrate on simple modules whatever they will be. I want them easy and fast to create and give them to the community so they can learn with various examples. And since we are near a new era (brrr) with the Xantia and pnRender engine coming, all will be templated for the occasion like the pncSimpleStats.

Voilà ! That is about what I've done and probably worth mentioning...


Where do you live?

I live in Paris - France, but was born in Canada.

What is your real-life job?

I work as a technicien and programmer on a professional software for music publishers. Mostly done in MS Access.

Tell me about your postnuke "career".

I'm not quite sure when I started but I'm a survivor of phpNuke. At first, I didn't like PostNuke (0.60 I think) and went back to phpNuke. But later, I felt that it wasn't serious. If I remember correctly, the only reason was the huge modules pool that was available for phpNuke then. But after a time, when you see that you will only use 1% of what is available, you take a peek behind other doors. And I came back to PostNuke (0.62) to make more tests. And got hooked.

As I wasn't very up-to-date about 'collaborative' programming, I was curious to discover how it was done. I made lots of tests with other CMS but was constantly driven back to PostNuke for various reasons or even to take a break. Then I got tired of testing and it was a natural decision to stick with PostNuke. The code under the hood had more common points with what I was exploring than the others.

With time, I was getting better at answering technical question and had a big presence in the french community. So David from Boomtchak ask me to co-administrate. When Boom went down for a time, another french support site went up and I was there again (Kaintech). I even been asked on Envolution-france but I didn't stayed long. Then the administrator of PostNuke-France ask me to take the lead because he couldn't stay, I took the opportunity and I'm there since then.

So I guess that for the french community, I'm known for the administrator hat, and for the rest of the world, for the lines I wrote.

When did you start working on your own module?

It was soon after deciding that PostNuke was the CMS I would stay with. Since I'm an self made programmer as that I didn't know much about php, I started by modifying already existing modules. That is how the UserHack was born. All it was doing at the time was giving the hability to users to choose their own password when registering. After that, I did various hack on the Downloads, the Web Links and when I gained confidence, I added an admin interface to the User Points mod and my first module was a FeedBack module. (Although many people made the same one, I didn't know at that time).

What is your development like?

I'm the "cliché" I guess, I work alone and like to be alone in the dark with a bottle of wine, my cigarette, and far away, the tv on. Yes, late at night when the bottle is empty, there are consequences on the coding. I won't say that it is the reason of course, but I try to make every line of code readable. Much needed at the end of the night. In fact, I think I put more time on how the code looks than how it looks when it is rendered. He he !

I like to consider myself the one that sometimes touches the soft spot of people. This is without being pretentious of course. I don't do very big things, I'm not the great programmer and my background may be slightly light, but the small things I do, people have been waiting for them. Like the first UserHack. When people were eager to have the possibility to choose their password at registration, I did it. When others or myself wanted an admin for the User Points, I did it also. And so on... I think that is mostly how I made my name.

I also rarely do something that I won't use myself. So many things I did were things that I wanted for myself in the first place. By chance, others were thinking the same.

The only tool that I consider worth mentioning is my code editor (if I can name it) : Crimson Editor (http://www.crimsoneditor.com), great syntax highlight, no crappy tabulations since the editor changes them in spaces and makes files readable the same way for everyone. I can't bare it anymore to read some code from others and taking half an hour only to make it clearer to read so I can understand it and fix or make modifications if needed. That is why I take my time to make my code so everyone on any computer sees the same thing.
You can also change code in files directly on your host with the ftp functionality. Perfect for newbies. Pros will probably move on to something that suits them more.

What is the biggest difficulty in your development?

I saw someone write "Time"... and that would be the same for me. It is not a PostNuke related problem since I am probably part of the rare ones to be happy that PostNuke is slow in development. I work hard in my professional job and I rarely sleep more than 3 or 4 hours a night so I'm very slow on creating any new things for PostNuke. People will say I never quite meet deadlines I propose and it's true (PostNuke related of course).

What features should the Postnuke .8 core have to simplify your work?

Good documentation and clear examples for newbies, intermediates and advanced users and developpers. I learned everytheverything from what others did and I'm still and will always be in a learning mode. The Example mod is a great start but when I have wanted to do something just a step more complicated, It has taken me awhile to find out how to do it. I have searched the smarty doc, and the Xantia code for a long time just to do something a little more complicated than what the Example mod was doing.

Which route will Postnuke/your module in your opinion go in the future?

I will follow its evolution and I have already started doing so. As I stated, I have already made a pnRender enabled module with the pncSimpleStats for practice and also to give another example for others and... I'm not sure but I think it may be the first non-official module done that way. And I intend to make more mods that are simple so people can have a look at them and say : "oooh, that I understand !".

What should users of your module regard?

I guess that one of my strong point is evolving with what the users want or doing the little thing that users were waiting for. When I look at my pncUserHack, between the first and the last ones, there are so much differences, it is freaky... but it is all what the users wanted at that time.

My weakest point would be the time I take to make something but that it is not something I have control over...

Anything else you always wanted to say about Postnuke/your module?

I know that there are developers like me hiding or keeping a low profile. I, myself, am often trying to keep a low profile because whenever I do something, it is always a great battle for me to support what I do because of time constraints. That is why I don't do much publicity. But I do my best to gain confidence about what I do and I hope to be able in the future to give more time to PostNuke, helping or coding. I hope that open minded developers that do have the time will get out of the dark and share their knowledge, skills and talent and contribute more to the development, documentation, support, etc.

Actual pnDevs are really, really great... but to give them a chance so they don't loose their mind, giving them a hand would be great.

Thank you very much for you time.

My pleasure ! And hoping my english wasn't too bad ! ;-)

Franky’s Homepage:

Generated on February 10, 2004.

Interview: Klavs Klavsen   (News)

What module(s) are you working on?

I help Øivind out a little with PagEd - he does some great work - and fast too !

I sent a few patches to Jason Judge, the creator of another great module called feproc (FormExpress Processor) - and as he didn't have an itch any more, he asked if I would like to take over maintainership, and so I have done, and released a few new versions with some features/fixes I needed myself :)

Other than that, I have made a small(!) addition to the FAQ module, that I hope will get in the PostNuke core soon - which makes the FAQ module require that you enter en email address, and emails the admin of the site, whenever someone enters a FAQ - they are both downloadable from my site http://VirkPaaNettet.dk. I've been trying to find out if it will be
included in the PostNuke core - cause if it does, I'd gladly add admin-options to the code, so one can select/deselect these additions - but no sense in doing this, if it's just going to be a bigger patch, for me to maintain seperately from the core of the FAQ module.

I also translate (or am working on a translation - delayed due to different reasons :) for PagEd, FormExpress, feproc and pncommerce when I get the time (and PostKart - available at my site, but you all know what happened to PostKart).

Basically, I don't like to re-invent the wheel - I'd rather improve it :) - and I always see if my suggested changes sit well (enough to be included in the main tree) with the maintainers of whatever I want to change/enhance a bit - as I don't want to be stuck maintaining patches that will never get in the real source. If I do make patches, I make them as small as possible, so that it's less of a fuzz to merge, each time the original source gets updated.

What is your real-life job?

I'm an Open Source and Security Consultant, and I have recently started a managed (ie. Only I mess with the source-code, and ensure it actually works - fixing problems, reporting them to the authors and adding features as my customers see fit) PostNuke hosting service, called http://VirkPaaNettet.dk My reasoning for doing this, was that I had used postnuke for more than a year, and was happy with it, so I figured that others could use this too and started it. My hope is that, if this becomes a success, I will contribute a percentage of my profit as donations to the maintainers of the FOSS that I heavily depend on, and if money allows, also sponsor whatever improvements my customers need.

I don't like to spend time, writing html for my site when I don't need to - I'm lazy, which I believe everybody should be. Less wars, better code :)

Tell me about your postnuke "career".

Well, my first real PostNuke site, was http://EnableIT.dk (original design, by a friend of mine, who'se a pro designer :) - and as you may be able to see, the pages are just the usual articles, with a few annoying things hacked away. This way to create pages, isn't very pretty IMHO, but then I found PagEd, which made me realize that with PN and PagEd I had a combination that could be used by everybody, even my own mom (and she does use it, for her up-and-coming company site :) - and started http://VirkPaaNettet.dk

When did you start working on your own module?

Well, I haven't written any modules of my own (only themes, like the one for EnableIT), I don't think I'm going to need to write my own module, anytime soon either, unless a customer wants to pay for it, as this is one of PostNuke's greatest strengths, the wealth of modules.

What is your development like?

I improve/fix where I need to and help out if I can and have the commitment to do so (I have to select my battles, as there are so many).

Do other people help you? How do you work together?

In regards to modules that I work on, I work via Instant-messaging with Øivind on the PagEd module.

I get great help from google, and people on different mailinglists, to which I'd like to extent a big THANK YOU, for lending me some time. I try to give back, by helping back on these lists, and on the lists of my local LUG (SSLUG), of which I'm a boardmember.

How big is the impact of the community on your development?

Well - google and mailinglists (and forums) are a big help. I'm hoping more people realise how great a module feproc is, and start using it :) If anybody is using it - do tell - I'd also like to build up the ToDo list, and people are more than welcome to submit patches ;)

What features should the Postnuke .8 core have to simplify your work?

The main thing I'd like is performance improvements in PostNuke - but until then, I'm going to up the performance with squid-2.5-reverse-proxy-patched.

The biggest issue there, is I can't seem to find anyone who can tell me why the POSTNUKESID is needed for anonymous users (and I haven't prioritized it enought to dig through and find out myself) - as I don't like that every page sends a cookie to my clients. the POSTNUKESID thing, should be deselectable - I can't see it's use for anything but polls, and
the poll module should set that cookie IMHO (by telling PN to do so - which needs to be possible - Xaraya has this feature now).

Which route will Postnuke/your module in your opinion go in the future?

I think PN will stay popular. The smarty templating thing in .8 will be really good - and I see modules like pncommerce and others already making their modules ready to handle this. If PN manages to make it easy for people to change the module templates - or just switch between different output (I mean easy, like my mom can do it via the menus), it will have become truely great.

Anything else you always wanted to say about Postnuke/your module?

Not really, I've said enough :)
Only thing I'll say is a big THANK YOU to all the FOSS developers, thanks to you I may be able to feed my family with the money earned by my virkpaanettet.dk service, and ie. get paid to develop/improve FOSS programs - could life be any better than that (except for kids and a family of course :)

Thank you very much for you time.

You're welcome.

Generated on September 25, 2003.

Interview: Chuck Steel   (News)

What module(s) are you working on?

I have written several modules myself that are publicly available including the Steel Knowledge Base, a simple database module and a task manager. I have also written some modules for work (our student technical support group uses PostNuke) and on a contract basis. My current project is a Reviews module that will include categories.

Where do you live?

East Berlin, PA.

What is your real-life job?

I coordinate technical support for the students at Gettysburg College, which means that I run our student helpdesk.

Tell me about your postnuke "career".

I looked at some of the other systems available and PN seemed to have the most documentation for programming modules available. I prefer to be able to find information on my own, rather than asking for help, and that didn't seem as likely with some of the other systems. The documentation that was available for PN at least gave me a starting point. PN also seemed to have a very active user community.

When did you start working on your own module?

I can't remember when I started my first module. Sometime during the 2002-2003 school year, I guess.

What is your development like? Do other people help you? How do you work together? How big is the impact of the community on your development?

Most of my development is done alone. I have been using DreamWeaver but will switch to something else once my development machine becomes linux. When I program at home I generally sit in the living room (wireless, yay) and watch TV at the same time. We have done some group projects with varying success. Our best approach so far has been to have one person develop (and document) the API functions and then have someone else work on the other areas. I am very concerned with interface consistency, so breaking things up too much becomes difficult. The community is a wonderful resource, although there aren't a lot of active module developers in the forums, so if you run into something really difficult, you might be out of luck.

What is the biggest difficulty in your development? And why? Is it a Postnuke inherent problem?

Time. I actually find that the PN environment makes some of the development work a lot easier. Once you understand the pnHTML functions a lot of the work becomes much less cumbersome. I wish I could use them in all of my web projects now.

What features should the Postnuke .8 core have to simplify your work?

I find the permissions system very hard to work within. It works well for module access, but if you want to have permissions on individual items that are dynamic, the permissions table could grow very rapidly to an unmanageable size. I could also benefit from functions to work with groups. I have written functions to determine if a person is a member of a group, for instance, but if that type of function was in the pnAPI, life would be much simpler.

Better support for html output. Some of the pnHTML commands don't support all of the parameters for the given tag. One example of this is that URL doesn't support a target, which means that if I want a link to open in a new windows, I have to output the html for the url manually. If you are going to implement functions to output html, it should be reasonable to make those functions fully support the given tag.

The security settings where someone gets logged out after x days. I think that this should be based on my last login. If I login to a site everyday, then I don't think that I should be asked to login every so often. If I don't visit a site for a while, then maybe.

What should users of your module regard and what is the weakest/strongest point in your module?

I wish that users wouldn't complain about small bugs not being fixed in something that they are getting for free. I don't know if this is common amongst open source development or not. Also, I provide forums on my pages to discuss problems and just like the forums on postnuke.com, no one bothers to check for previous threads that might help them. And my forums
aren't even that big, most of them don't even go to a second page!

Anything else you always wanted to say about Postnuke/your module?

I really enjoy PostNuke. I use it on several sites and while I occaisonally have issues, it has made my life and work much better. Right now my biggest complaint is that there isn't a paypal donations button on the postnuke site. I would love to throw a few bucks towards the development efforts, even if no one is throwing any my way.


Thank you very much for you time.

No, thank you.

Generated on September 18, 2003.

PivotLegal.org - PostNuke Powered Societal Change   (News)

longtime user of PostNuke - I am happy to announce a new site employing the world's most powerful and dynamic Content Management System

http://www.PivotLegal.org

Pivot is a non-profit society dedicated to advancing the interests and improving the lives of marginalized persons through law reform, legal education, and strategic legal action.

Members now have access to web forums, the ability to submit press releases and news, a comprehensive resource section, as well as the ability to interact with the site itself by posting article notes and comments.

If you haven't already done so, you are invited to join our site. Membership is free and open to anyone. You can join by clicking here

Highlights of Enhanced PivotLegal.org

PivotLegal.org Forums: Bulletin board style forum for discussion of news and issues. You can access the Forums here

Images of Shame: A new section focusing on photographic evidence of acts of injustice. Members can submit their own photos for inclusion. You can view these images here

Resource Area: PivotLegal.org aims to establish the largest index of web-related resources of interest to marginalized individuals and groups. Members of PivotLegal.org have the option of rating and commenting on other sites in the Resource section. You can access these Resources by clicking here...Additionally, you may submit your own Resources here

BannerArt: If your organization wishes to promote itself - send a standard 468x60 banner to peter@pivotlegal.org for inclusion in this rotating advertising section. If you'd like a banner CREATED for your organization, simply indicate that in an email to peter@pivotlegal.org (payment is optional). BannerArt appears at the bottom of every Web page on http://PivotLegal.org

- 30 -

For More Information regarding PivotLegal.org:

Peter Zahoruk, Information Technologist
peter@pivotlegal.org
Pivot Legal Society

About Pivot: Pivot is a non-profit society dedicated to advancing the interests and improving the lives of marginalized persons through law reform, legal education, and strategic legal action.

For more information about Pivot visit PivotLegal.org

To donate to Pivot via PayPal, use donations@pivotlegal.org as the recipient

Generated on November 21, 2002.

Help wanted   (News)

#1 a password protected browsable database of members names

#2 new member signup area (with corresponding admin approval denial control panel) who's functions including e-mailing a member his password and login name on a monthly basis (kind of like the mailman system)

#3 some moderate interaction with a sendmail .aliases file

#4 current member's input screen where they can edit their own info

#5 an admin Control panel that gives admin ability to:

- reset member passwords

- add new members

- edit members

- edit member e-mail addresses ( I have a program for this that could be integrated)

- simple database backup to a "flat file" within the site

#6 system can be tared/zipped up and moved to new host if necessary with no major hassles (adjusting an absolute path within a config file in not considered to be a problem



Those are the listed REQUIREMENTS

The want list PHP/SQL would be the preferred method for this the current system uses cgi and a csv file to store the info. The ability to tell the program that it is operating with phpnuke and to "share cookies" IE the user could use a phpnuke database for user name and password functions. At the same time if phpnuke was removed the program would retain its own copy of the username and password for that user.



All seriously interested persons please contact webmaster@secondcavalry.com

Limited funding is available for this project and all current funds were gathered by donations from the Veterans group for this project.

Generated on July 6, 2001.