Re: Applications processed + future renewals

Hi Eric.
        It looks cool ;)
We definitely need a better system that the manual one at the moment. Hopefully, the new system is not too heavy.

        What did you use as the DB? How many tables have you defined?
Vincent's suggestion of 2 tables seem reasonable. We will need a field for when the membership expires to send out reminder 2 months before hand.
Ultimately we could transfer the complete mailing list of foundation-announce to here even ;)


Eric Baudais wrote:
On Tue, Jul 01, 2003 at 04:06:10PM +0200, Vincent Untz wrote:

Sorry for answering so late :/

Le Sat, 14 Jun 2003 15:30:01 -0500, Eric Baudais a ecrit :


I have started on the membership database.  You can view the web
interface at This is just a start to the
database.  The only part of the web interface working is searching the
database and showing all members in the database.  Right now there are
only 4 entries in the database for testing purposes.  I'll be adding a
way to insert new members into the database (the insert button doesn't

I lookeed at this. It looks great. But I think there's something we
should do : we should have to DB tables, one for the applications and
one for the members. Thus, we can have a record of all applications. And
we have an easy access to all the current members. If someone applies
twice, we'll still have both applications and this sounds important to
me. What do you think about it ?

Are you wanting to place the body of the application we receive from
the web form in the database?  Or are you wanting to display a
separate list of applicants and list of members, but keep sending the
applications to the membership committee list?

What I really need help on is to convert the flat file into a SQL file
to insert in to the database I've made.  I haven't been very
successful extracting the data from our flat file.

I can work on that if you haven't found a solution yet.

I haven't done anything with regards to this.  I think the
membership_new.txt file will be easy to parse.  However the
application_status.txt file is not so easy.  Any help on this part is

Currently there isn't a way to keep track of renewals in the database
either.  I plan to work on that issue once I have made the web
interfaces to display, insert, and delete entries from the database.

The first phase of the membership database is complete.  You can
display, insert, edit, and delete any entries in the membership
database.  The second phase will consist of adding renewals to the
database, automatically emailing members a renewal reminder,
automatically entering new applicants information into the database,
and some form of restricted access either by .htpasswd or some form of
php session management.

Any comments, suggestions, or ideas about the membership database and
web interface is welcome.

Eric Baudais
Membership-committee mailing list
Membership-committee gnome org


Ghee Teo

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]