No on both counts -- you just need to be able to make corrections to the S2 layer code, and I'll do the work of patching the layouts. There might be a few bugs that *are* perl-related, but the majority will be fixing S2 layers.
I *believe* that all of the code is publically available in our repositories -- possibly not on the site, though -- but in those cases the solution is "copy/paste out of the repository and make a new layer" ;)
A while back, I posted code to update Tranquility II - can that be implemented? It fixed some non-compliancy with xhtml 1.0 and added a userpic toggle to the basic customisations, here: http://community.livejournal.com/lj_dev/732239.html
Will this list help with gathering bugs (all/most Flexible Squares-specific).
Er, must warn you that some of those are pretty incomprehensible. I'll try to clean it up or something. Also, not all of those are bugs. Some are just things that would make the layout easier to customize or that users seem to really really want (quickreply, commentbar links).
At least for the first round, I'm gonna be pulling from the bugs that came in through the Support board, but if those are boring / if we empty that list / whatever, I'll take other ones too. *g* (Also, good call on quickreply -- I might see if I can work that into one of these.)
Have fun! Most of the FS-related bugs on the board scare me -- seem to be mostly tied to peekaboo, which, uh, scares me. ;) (Yay! Looking forward to getting quickreply in!)
Hm, I think I'll go see if I can lure more people to the lj_dev comm and the contest right now.
* Possible post linking to this in lj_style. I think it would also be good to post a link in many of the more active style communities--I know Smooth Sailing's s2smoothsailing hasn't had one posted, and if you wanted to, I could post there.
* It's possible that some people who might want to participate will be hindered by the lack of a current paid account to test with. I wouldn't want people to use this as an opportunity to get a free account, however, so what I would suggest is giving out paid accounts or paid communities with random jumbles of letters and numbers for names available for a month to those who request them. That will limit their utility elsewhere so abuse does not happen, but still allow the person in question to have a test bed.
on the topic of needing paid accounts to edit layers, they could allow creation of accounts on a test server again. that would also not clutter the namespace on LiveJournal.
however, one other thing that they might be able to do is to create these accounts in the form that you describe, and then del'n'purge 'em when the hackathon is finished.
* I'll try to come up with a solution to that -- I don't think there'll be too many people who fit into that category, but I'll do what I can to accommodate them.
I don't think there will either, but if there are people out there willing and able, it'd be nice to make sure they were somehow included, and I'm sure there's a way to do it without attracting freeloaders.
Comments 20
Reply
Reply
Reply
Reply
http://community.livejournal.com/lj_dev/732239.html
Reply
Reply
Reply
Reply
Er, must warn you that some of those are pretty incomprehensible. I'll try to clean it up or something. Also, not all of those are bugs. Some are just things that would make the layout easier to customize or that users seem to really really want (quickreply, commentbar links).
Reply
Reply
Hm, I think I'll go see if I can lure more people to the lj_dev comm and the contest right now.
Reply
* Possible post linking to this in lj_style. I think it would also be good to post a link in many of the more active style communities--I know Smooth Sailing's s2smoothsailing hasn't had one posted, and if you wanted to, I could post there.
* It's possible that some people who might want to participate will be hindered by the lack of a current paid account to test with. I wouldn't want people to use this as an opportunity to get a free account, however, so what I would suggest is giving out paid accounts or paid communities with random jumbles of letters and numbers for names available for a month to those who request them. That will limit their utility elsewhere so abuse does not happen, but still allow the person in question to have a test bed.
Reply
however, one other thing that they might be able to do is to create these accounts in the form that you describe, and then del'n'purge 'em when the hackathon is finished.
Reply
* I'll try to come up with a solution to that -- I don't think there'll be too many people who fit into that category, but I'll do what I can to accommodate them.
Reply
Reply
Leave a comment