fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu

With [staff profile] denise's help (the bulk of this was from her really!), we've made major changes to the dev-facing wiki documentation for clarity.

Among other things:

  • merged multiple/redundant pages and sections

  • improved linking

  • (hopefully) reduced the complexity of paths through the wiki for someone just getting started

The biggest change is to Dev Getting Started, which is now greatly expanded, with a much clearer flow, and more focus on someone totally new to DW/development. The resources for someone more experienced have been moved to Dev Quick Start .

The contents of Version Control have been merged with Newbie Guide: How To in Git and the latter is the canonical page for git info -- though now I'm tempted to go rename it to Version Control because it's shorter. Git How To? ;)

Git instructions in some pages have been updated to be much simpler with a pointer to the appropriate section in the git commands in case that's needed.

And the Directory Structure has been expanded to cover more subdirectories.

Beginner Dev Checklist needs some more effort to pull it apart: plan is to integrate it into other pages as appropriate and then get rid of it (since it's not sufficiently different from Dev Getting Started to warrant its own page)

Would appreciate if you poked around through the various pages and let me know if there's anything still left unclear, or if you're aware of similar pages that can be merged into these existing ones!

pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
swaldman: A cute fluffy sheep curled up dreaming of Dreamwidth. Labelled "Simon: Bodger". (dw-dev)
[personal profile] swaldman
So my pull request re posting notifications of new Dreamwidth entries to Twitter got reviewed, and has comments that need to be addressed. However, I don't have time or headspace to devote to DW dev work at the moment, so if this is going to make it in before it bitrots completely, it would probably be best if somebody else took it on. This leads to two questions,
  1. Anybody want to take this on? I think it's mostly there, but needs tweaking as per comments. And probably some fairly thorough re-testing, since things may have changed with Twitter and Net::Twitter since I wrote it 18 months ago.
  2. More generally, what should I do in this scenario? Is there some way in which I can unassign myself from the PR? (I'm not sure that there even is an Issue to unassign myself from; I did this work while we were in bugzilla)
Thanks.
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
The workflow given in http://wiki.dreamwidth.net/wiki/index.php/Routing_and_Template_Cookbook:_BML_Conversion_Workflow doesn't indicate what to do when you find yourself in the presence of a widget, like for htdocs/support/submit.bml. Some questions an addition could cover:
- Can/Should I use the widget itself directly in a controller?
- Which parts of the widget need to go where?
- When is it safe to get rid of the widget itself? (eg, how do I know it's not used anywhere else)

I probably forgot some questions/issues. Discuss here and I'll try to summarize to the wiki?
kareila: (Default)
[personal profile] kareila
A few months ago, I started scheduling regular dev chat meetings in an effort to increase awareness of our development efforts and discuss how to deal with common issues we all face in the course of development.

I think a lot of good has come from these chats. However, over the last six weeks or so, participation has fallen way off, and I'm no longer convinced they can continue to serve a useful purpose in their current form.

If it's a scheduling issue, I'm happy to move it around to get more attendance. I've asked before for alternative times and gotten no responses. I had hoped that by scheduling it to occur at the same time every couple of weeks, that would allow people to plan ahead to arrange their availability to attend. If it would work better to poll everyone for a preferred time for each meeting, I can try that for a while.

If it's not a scheduling issue, I'd like to know why more people aren't showing up to participate. It was made clear to me in the discussion here that there was definitely a perceived need for something like this three months ago. Has that need disappeared? Should we be trying to meet it in a different way?

Basically I want to do whatever I can to help facilitate communication in the development community, but I want to make sure my efforts are having the desired effect. Please comment if you have any thoughts on the matter. Thanks.
swaldman: A cute fluffy sheep curled up dreaming of Dreamwidth. Labelled "Simon: Bodger". (dw-dev)
[personal profile] swaldman
Nice flowchart here.

It's not new, but I haven't seen it here before :-)
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Also, I'm curious: if you have a coding blog, would you like links to recent entries rounded up on dw_dev? If so (no obligation), feel free to comment with links and someone will compile them and post a new entry here.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
I've had my talk, "When Your Codebase Is Nearly Old Enough To Vote", accepted at Linux Conf Australia in January. Every time I swear I'm going to start developing my talk earlier than "the week before the conference", and this year is no different ...

Description of the talk:
Read more... )

With that in mind, are there any particular horror stories people think I should tell? I mean, I have a general outline in my head already, and I'm definitely going to be talking about things like "what happens when you invent something because you need it, then somebody else invents the same thing two years later and that's the version that takes off instead" (*cough* BML *cough*) and the like, but I'd like to tell some funny stories like "that time we wanted to make it possible for people with a default icon to select 'no icon' at the time they post, only to discover that the reason no icon displays when people haven't chosen a default icon was, in fact, due to a twelve-year-old bug" and stuff like that.
kareila: (embarrassed)
[personal profile] kareila
There will not be a dev chat meeting today unless someone else shows up for me to talk to, because Mark and Fu are on vacation.

However, I will be around trying to hack on DW stuff for the next few hours, so come find me if you want to pick my brain about anything.

The next scheduled meeting time is on Saturday, September 13, at 12 pm EDT.
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
[personal profile] sophie
I just updated LWPx::ParanoidAgent and Net::SSL on the Dreamhacks server - something that I've needed to do for some time. In the process about seventy bajillion other modules that they relied on needed to be updated, too (mainly to do with HTTP/SSL stuff) so the following modules (and any submodules included in their distribution) are now at their most recent (and the links given lead to the exact versions installed from CPAN):

23 different distributions in total )

As this is rather a lot of modules, some of which can be core to various things that the codebase does, you should restart your Apache if it's currently running; there may be errors otherwise. Also, it's possible that the update of these modules might somehow cause brokenness in some areas on the Dreamhacks server; please do comment here if that's the case (or open a GitHub issue).

(Please note: This only applies to brokenness on the Dreamhacks server. Nothing has changed on dreamwidth.org, so any issues there should be raised in a Support request as usual.)
azurelunatic: Azz and best friend grabbing each other's noses.  (Default)
[personal profile] azurelunatic
This tour is a group effort. Thanks to [personal profile] kareila for rounding up and coding all the issue links! I provided the descriptions.

Here we have a lot of fixes for styles issues, and a lot of stuff from [staff profile] fu! This is a more prompt release than some, because everybody was really anxious to get some of the mobile wonkiness introduced with the last update fixed in this one. We also have stuff from [staff profile] denise, [staff profile] mark, [personal profile] hotlevel4, and [personal profile] exor674.

This code tour is live: the code push entry is over in [site community profile] dw_maintenance as usual.

Read more... )
kareila: Rosie the Riveter "We Can Do It!" with a DW swirl (dw)
[personal profile] kareila
If you weren't able to make today's meeting in #dreamwidth-dev, the next meeting will be on Saturday, August 23, at 12 pm EDT. Also there will be another hack date on Sunday, August 17, also at 12 pm EDT.

Here's a list of topics we discussed today, and most of them will probably be revisited next time:

  • code push tomorrow, should fix issues with new mobile styles
  • Github Issues revamped, updated docs on wiki
  • possible alternative project trackers and chat platforms
  • scheduled another social hack time for 8/17
  • encourage "what are we working on" discussion/issues outside of IRC
  • reconsidering how we name/advertise release branches


In attendance were myself, Afuna, zorkian, exor674, and V_PauAmma_V.

Raw chat log under the cut. )
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Note: as mentioned in http://dw-dev-training.dreamwidth.org/58411.html, this month's question thread is in dw_dev instead of dw_dev_training. I plan for this to continue if everyone is comfortable with it, so feel free to comment (either way) about this change too.

ETA: can someone able to create tags on dw_dev add "questions" to this entry? Done, thanks!
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu
Forgot to say -- if you forget to claim a bug formally, but you submit a pull request that refers to that bug using the "#123" format in a commit, then that will also automatically assign the bug to you.
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu
Given how much work we're doing on styles, we've decided that instead of doing pushes one-by-one, we're going to get the styles to a good push state and then push them all in one go + accompanying news post.

So no more hotfixes off the current release branch, let's go off develop :)
kaberett: A sleeping koalasheep (Avatar: the Last Airbender), with the dreamwidth logo above. (dreamkoalasheep)
[personal profile] kaberett
I've synthesised discussions about and practical use of GHI into a single wiki page. Please shout if you want anything added or changed!

I've also gone through and replaced as many references to Bugzilla with references to GHI as (1) makes sense and (2) I am immediately able. There's about 20 pages still on my hit-list, not all of which I have the knowledge to deal with - if you feel like pitching in, please take one and let me know when it's done (or, if you don't have wiki access, let me know what the appropriate edits would be).

List of pages outstanding )
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu
We discovered that you have to be a committer on a repository in order to claim a bug for yourself on Github. If you're not one, you have to ask someone to assign the bug to you.

This didn't really seem feasible, so we've fixed it. You can now claim an issue by leaving a comment with the words "claim", "claimed", or "claiming".

Case doesn't matter -- you can use capital letters if you want. You can also have other words be part of the comment, so you don't need to memorize a specific format. "I'm claiming this" will work just as well as "Claimed!".

Claiming will only work if the current issue is not yet claimed -- this will avoid the problem of accidentally grabbing the bug from someone else during a long discussion about claiming something else in a different context.

You *do* need to be part of the Dreamwidth contributors team on Github before assigning issues will work so we've gone and added everyone who's been active in the past year (if you got an email from Github welcoming you the Dreamwidth contributors team that's what that's about!). If you're a new contributor, you'll be automatically added when you give your CLA to [staff profile] denise.

For existing contributors, do double-check if you're on any of the Dreamwidth teams. If it shows you a list of teams you're on, you're good! If we missed you somehow and tells you that you're not on any teams, let us know and we'll add you ASAP.
kareila: (Default)
[personal profile] kareila
Hi all,

I'm moving the next chat meeting back a week, to Saturday, August 9, at 12 pm EDT. I hope this doesn't inconvenience any one, but neither Fey nor I can promise to be around this coming weekend.

I hope the hack date on Sunday was productive! Hopefully I can be there for the next one. :)
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu

We have two main branches in the Dreamwidth repositories: master and develop.

master was intended to be used but... never really got any love.

So here's what I propose: remove all the instructions in our documentation which mention master, and just have 'develop`.

Since develop is where all work goes, nothing in the dev workflow will officially change. But occasionally we have accidents where master gets merged into developinstead of the other way around, or someone finds themselves on master when they should be on develop instead -- and removing any mention of master from our instructions should prevent that from ever happening again.

As for what will happen to master... we never actually used it, and at this point ingrained habits for develop + all setups old and new assume develop, so I suggest we continue not using master the way we currently do.

mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark
FYI -- the aforementioned "let's sit down and work on things!" time is going on now in IRC and will be for a couple of hours. I've you've a project you've been meaning to work on but haven't found the time or motivation, come on over and join us!

Profile

dw_dev: The word "develop" using the Swirly D logo.  (Default)
Dreamwidth Open Source Development

October 2014

S M T W T F S
   1234
5678 91011
1213 1415161718
19202122232425
262728293031 

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 24th, 2014 11:16 am
Powered by Dreamwidth Studios