The future of PIFT

boombatower - February 11, 2009 - 20:02

Project:	Project issue file testing
Version:	6.x-2.x-dev
Component:	Miscellaneous
Category:	task
Priority:	normal
Assigned:	Amazon
Status:	closed

After a number of discussions in IRC, hunmonk has made it clear that he wishes to be less involved in the day-to-day activities of the testing framework. From my understanding he also is interested in letting me take over PIFT for 2.x development. I'd like to gather all the thoughts on this subject and get a consensus and a plan.

The following is a summary of my understanding/thoughts:

Currently developing PIFR 2.x and hope to complete within next 2-3 weeks.
Need PIFT 2.x completed along side PIFR, hopefully in same time-frame. I'm happy to write the code, just need commit access.
Debugging and management of PIFT on drupal.org seems to be part of what hunmonk is trying to get away from. Not sure if we should just keep it the way it is...or if I should get some access to d.o things in order to be able to manage the testing framework completely?

The first two points seems fairly straight forward. The last one needs some discussion.

Another item for thought, is how to go about deploying PIFR/PIFT 2.x. Possibly stage on project.drupal.org? I will obviously test locally, but not sure what the thought is.

» Login or register to post comments

#1

andreiashu - February 13, 2009 - 02:01

subscribing

#2

hunmonk - February 16, 2009 - 13:41

i've basically completed my last major task, which is an installation script for testing servers. outside of the installation of the LAMP stack, CVS, a few other basic pieces or software, and the configuration of the firewall, this script takes care of setting up everything related to a testing server, including the full drupal installation, and creation of all testing administrator accounts on the machine.

the remaining tasks there are:

run a server through the process and hook it up to t.d.o to make sure it's working correctly.
get the usernames and SSH pubkeys for anybody that we want to be a server admin.
convert the existing test servers to use this installation script so we have a consistent install across servers.
write up a small handbook page on t.d.o for the admins to give them some notes on how to navigate the testing machines.

after this process is completed, we can move on to the handoff of PIFT. i see no reason why we can't have the above done by the end of this week.

couple of other thoughts:

we should definitely use a staging area to practice the rollout of 2.x
although i don't want to be involved with any day to day development or maintenance of 2.x, i can make myself available to answer questions and perform simple admin maintenance on drupal.org until all that smooths out.

#3

boombatower - February 16, 2009 - 18:49

Sounds good. Let me know when you want to do the re-configuration of the servers, or might be easier if you do it whenever your free.

#4

hunmonk - February 16, 2009 - 21:13

Status:

active

» postponed (maintainer needs more info)

step 1 from #2 has been completed. we now need the list of server admins and their SSH pubkeys.

#5

boombatower - February 16, 2009 - 21:43

Attachment	Size
id_rsa.pub_.txt	400 bytes

#6

Amazon - February 16, 2009 - 23:13

Assigned to:

Anonymous

» Amazon

Ok, the list of people who offered servers is on http://testing.drupal.org. I'll get their contact information and point them to a write up. It would be good to have the instructions written up as blog post to Drupal planet.

Cheers,
Kieran

#7

boombatower - October 22, 2009 - 19:17

Status:

postponed (maintainer needs more info)

» fixed

#8

System Message - November 5, 2009 - 19:20

Status:

fixed

» closed

Automatically closed -- issue fixed for 2 weeks with no activity.

The future of PIFT

Jump to:

#1

#2

#3

#4

#5

#6

#7

#8

User login

Contributor links