![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
A little organization and updates!
Hi all!
I've been doing some poking around and realized that I don't have a good overall state-of-the-DW-development. I have some vague ideas about what some people are working on and interested in, but I wanted to make those vague ideas become a bit less vague. :)
If you have a few minutes, I'd appreciate you taking the time to answer a couple of quick questions here!
- Are you actively working on a bug (or several) right now? Which ones?
- What are you interested in working on -- broadly or narrowly, what do you want to do? (Or are you just open for suggestions?)
- Is there anything explicitly blocking you from doing what you want? (Knowledge, someone has the bug claimed for a year, need a hand with something, etc.)
- Free form! Anything you want to say or ask. :)
I also want us to have another development focused chat like we did some months ago. I think the last one I did was well timed for US developers but bad for EU, so I'll go the other way this time. I'm thinking something like 8AM Pacific which is midnight for ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
fu and 4PM UTC on a Sunday. Reasonable?
Thanks!
no subject
2. Longer term I've been eyeing up the various bugs related to exporting journals in various formats. There seems to be a fair bit of work involved there but it's something I'd be interested in taking a look at.
3. Time really, though also just generally working with a large code base which I don't work with intensively enough to just know where stuff is (I keep having to check back my notes). And for 2152 Template Toolkit turned out to have a surprisingly steep learning curve for me.
4. I've found the Most Wanted Bug List helpful when looking for a project to tackle. I keep thinking I should check out the IRC more, but I'm not really a good "chatter".
no subject
Exporting is definitely a big project. I don't know how much detail we have on any bugs that are open for it, but I definitely recommend making it something that runs external to the core service. I.e., build it using the APIs and use that as a tug to make the APIs better if they're deficient.
(I'm assuming that with a skill level capable of handling journal exports, you can handle some API stuff! And hey, we're here to help if you get stuck or need a hand with that!)
I totally agree about IRC. I'm there all of the time, but for the life of me I can't chat. Maybe at my best I can spend a few minutes doing some small-talk, but I always end up wandering off and getting sidetracked into other things. I feel bad about it, heh.
Thanks for taking the time to comment and to work on Dreamwidth! :)
no subject
My guess, though I've not tracked it down, is that there is an existence check on the keyword somewhere and perl evaluates it to 0/false because of the leading 0 in the string.
IIRC, last time I looked at the export bugs there were a couple, including general improvement of the existing export tool, and a specific request to export as pdf. My thought was to find my way around the API (*sigh* document where necessary), and that ideally dreamwidth probably only wants to support exporting to a single format (XML) - at least for basic accounts. But if the XML were well enough documented then third parties (or dreamwidth could provide the source code but not host the application) could easily write conversion tools to act on the XML. I'll need to get the hang of the queuing system as well - so lots of learning involved.
no subject