kareila: Rosie the Riveter "We Can Do It!" with a DW swirl (dw)
[personal profile] kareila
This is the first run of our new code tour generator - it seems to be including more issues that were closed without code changes, and I tried to edit out most of those, but I expect the ride might be extra bumpy. Please make sure your seat belts are fastened and keep your hands inside the vehicle at all times.

Also, this tour is full of tons of boring backend changes and I wasn't able to find much humor in them, so the writeup will be less entertaining than usual. I do apologize and will not be offended if you decide to skip this tour and wait for a more interesting one. However, if you are willing to brave the ride, you will discover a few fascinating features, such as support for multiple sticky posts and a redesign of the new tag navigation feature. Also you will find your journey is more secure, as this code push will bring support for HTTPS everywhere on the site.

Onward!

GET IN THE CAR IT'S A CODE TOUR )
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.
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.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
This year, Dreamwidth will be attending Open Source Bridge as our major conference, and like in previous years, we want to bring YOU with us.

OSB runs June 23–26, 2015 in Portland, OR. It's an absolutely wonderful conference -- probably my favorite conference out there. There are all kinds of fabulous talks by all kinds of fabulous people, but even better (IMO) is the hacker lounge, which is huge and full of comfy chairs and fun stuff to play with and really fascinating people to talk to. We'd love for you to be one of those people, and we'll pay to make that happen.

It does not matter if you think you're a Real Developer(™) or not: OSB is my favorite conference for many reasons, and one of them is how there's something for people at every level of experience. Don't let your impostor syndrome keep you from coming, please! If you're reading this, we want you to consider joining us. Really. Not only will you get to attend a really great conference, but we always do a bunch of DW hacking in-person as well. (And there's usually a code push, which means you'll get to hear all the swearing in person, which I am reliably told is hilarious.)

This offer will be open to anyone who has submitted 5 or more pull requests (big, small, or anything in between) by June 1. (We'll be generous there -- if you want to do one big huge thing with massive amounts of effort instead, come see me and we'll talk.) (Also, I was asked if that was "5 PRs between now and 1 Jun" or "5 PRs ever" -- I'll say "5 PRs since 1 Jan", since the goal here is to bring together people who are actively working on DW.) If you do, we will pay for:

* Your conference admission (which includes lunch)
* Your housing in Portland (either in a hotel room or a rental house, depending on how many people we have -- usually it's been hotel rooms with two double beds, each person getting their own bed but sharing the room with one other person)
* Your airfare, round trip from your home airport to PDX (yes, this includes from outside the US!)
* At least one nice group dinner during the trip, and possibly others, depending.

(NB: Generally speaking, we find that on these trips people spend between $200-$300 on other travel costs (meals that aren't covered by DW, tickets for the light rail to/from the airport, etc). If you'd like to come but that cost would be a hardship for you, come talk to me privately.)

This offer will be limited to the first 15 people who sign up when we open actual signups, but we've never hit that number before. (I really just mention it to guard against the budget running over.) I'll be posting a signup post as we get closer to the actual conference, but I wanted to let people know the plan early so you can all get started working on things!

I know that the open issues are a bit thin right now, since we're still rebuilding the list. If you don't see anything you want to work on there, browse through the bugzilla: migrated (misnomer of a) tag in [site community profile] dw_suggestions: all of those are suggestions that have been approved, but not yet implemented. (I'll do another pass through them next week just to make sure they're up to date.) They haven't been migrated into GitHub Issues yet, but if you see something that you want to work on, open a new issue and copy/paste the text of the suggestion into it, then start work on it.

Also, you can still submit a talk for consideration! (Talk proposals close 7 Mar.) I will repeat my standing offer, which is that if you have a talk accepted, I'll work with you on creating, rehearsing, and delivering the talk beforehand as much as you'd like.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
Open Source Bridge talk proposals (and keynote nominations!) are open. Deadline is 11:59 PM PT (UTC-8:00) on March 7, 2015.

OSB is a great conference with a wide diversity of talks on all kinds of open-source related issues, not just programming! We will be going this year, and I'd love to have a bunch of people from DW giving talks. I will happily help you put yoru talk together. :)
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
I created the Explanations wiki page after seeing [staff profile] mark waving the code machete tonight: he took out a lot of old and unused stuff, which is great, but a few (very out of date) old server-admin documentation files that were casualties had some explanations of things that I don't think are documented anywhere else.

That does not mean the entire server-admin documentation should survive -- out of date documentation is often worse than no documentation! -- but between that and the talk I gave at LCA, "When Your Codebase Is Nearly Old Enough To Vote", it occurred to me that we should probably document a few of those things that live in our heads that we find ourselves explaining to new contributors -- things like why an entry URL uses the anum and not the jitemid, why you can't just change a text string in a patch and have it update the text on the live site, why you occasionally hear oldtimers calling the Recent Entries page 'lastn', stuff like that.

So, if you've been around for a while and can think of a few things that wouldn't necessarily make sense right off the top of your head -- or if you're new and ran into one or more of those things at some point and had to have someone explain them to you -- please add them to that page! As I said in my talk: institutional memory is a great thing to have, but a lousy thing to have to rely on.
kareila: Rosie the Riveter "We Can Do It!" with a DW swirl (dw)
[personal profile] kareila
Every few months, I run through [site community profile] changelog compiling a list of who has been contributing patches to our code repository, with the understanding that this is not a competition, or any sort of "high score" list. It's intended as a guide for casual developers, to discern not only our most prolific contributors, but also those who have contributed to the project most recently and therefore would be more likely to provide a timely, informed response to development questions. That is why the list is sorted by "Latest" instead of "Changes".

In general, one commit on Github equals one point in the "Changes" column, but fractional points are awarded for collaborative efforts — the most common example being a new S2 theme, where usually half credit is awarded to the theme author and the other half to the person who converts the theme into a code patch. Due to the nature of development, some changes are massive contributions of new code, and others are tiny tweaks; there is no correlation with the amount of effort involved. We are grateful to everyone who helps to improve Dreamwidth, in ways large or small.

I last compiled this list at the beginning of July. Since that time, we have welcomed two new contributors: [personal profile] horrorcheck and [personal profile] azurelunatic. Congratulations and thank you again!

  #  User                      Changes     Latest
  1. fu                           2002     Tue Jan 06 18:01:45 2015 UTC
  2. hotlevel4                      36     Mon Dec 22 17:05:18 2014 UTC
  3. azurelunatic                    3     Mon Dec 08 18:51:00 2014 UTC
  4. pauamma                       119     Mon Dec 01 13:40:04 2014 UTC
  5. baggyeyes                     2.5     Thu Nov 13 18:02:17 2014 UTC
  6. horrorcheck                     2     Sun Sep 21 02:28:31 2014 UTC
  7. woggy                           7     Wed Sep 03 03:23:30 2014 UTC
  8. denise                     412.08     Tue Aug 12 15:29:38 2014 UTC
  9. exor674                       335     Sun Aug 10 00:02:58 2014 UTC
 10. liv                            33     Tue Aug 05 16:55:54 2014 UTC

 11. mark                        523.5     Sun Jul 27 17:45:15 2014 UTC
 12. kareila                     801.5     Sun Jul 13 03:10:35 2014 UTC
 13. stormerider                    10     Sun Jun 29 04:55:38 2014 UTC
 14. kaberett                       14     Sat Jun 28 06:40:28 2014 UTC
 15. sophie                         57     Wed Jun 25 12:37:36 2014 UTC
 16. momijizukamori             210.16     Sat Jun 21 23:07:59 2014 UTC
 17. darael                          8     Mon May 12 13:43:30 2014 UTC
 18. fhocutt                         4     Thu Apr 03 06:24:15 2014 UTC
 19. ninetydegrees              693.93     Mon Mar 03 20:22:10 2014 UTC
 20. nornoriel                    15.5     Thu Feb 27 19:58:39 2014 UTC 
The rest of the list... (146 total) )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
This code tour covers commits from 11 August onward! I may have missed some (it's harder to get a code tour out of Github than it was out of Bugzilla) but I should have most of them. :)

In this code tour, we welcome emhoracek's first contribution! yay! We also welcome [personal profile] azurelunatic's first code patch -- she's been contributing for a while, but this is the first code contribution. Yay!


Code tour, 11 August - 18 January )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
We need someone to do a code tour! It's been a while since the last one. (We are going to be putting processes into place to keep us from forgetting how long it's been since we've done these things, really we are.)

Nevermind; I'll get it!
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.
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu
A critical security vulnerability has been announced for Git which affects Windows/Mac. Make sure you update your clients!

The Github announcement has a bunch of useful links to clients. If you're on a Mac and use Homebrew, that one has also been updated. I believe macports has as well, but double-check to be sure.
momijizukamori: (dreamsheep | styles)
[personal profile] momijizukamori
Not dead! Just busy with life. But Fu is in the process of converting the widgets on /customize to something less ridiculous, which gives me time to prod some of the problems that have been stumping me.

1) Preserving search results
The order of actions to generate a page of results from the advanced search, as I have it right now, goes like this:
User checks boxes to indicate choices -> user presses 'search' button -> button triggers POST actions -> a query is generated as one of these actions -> query goes to worker -> worker performs search -> worker sends back a list of theme ids

The problem is that POST data is lost on reload/page change, so when you click to see the second page of results (if there are more than one page), all of the query and the results vanish. Most of our other ways of grabbing a set of layouts (by base style, by designer, etc) append the query string to the URL, which is then hidden from the user via routing, but even just the list of search elements has the potential to get unwieldy fast (and the return list is worse)

2) The auto-categorizer
I don't have this working yet because it's not necessary for the new search, just... nice, given we have almost fifteen hundred themes (!!!). The script needs to pull hexcodes out of the style layers (which is all text to the perspective of anything not the S2 compiler). That seems to say 'regex' to me but I don't know if that's safe/the best way to do it.
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.
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
If you were having issues with reinstalls or database updates on the Dreamhack machine, you should be good to go now if you retry what was failing before. The code needed a new version of the Locale::Codes distribution, meaning that update-db.pl wouldn't work. It should work now!

(Yes, reinstalls work again; I've been meaning to announce it here for ages, but I've kept forgetting. They work now by reinstalling from your personal Git repositories; there's currently no means to automatically nuke those repositories and re-fork, so if you need to do that, let me know.)
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 have just installed Template Toolkit 2.26 on the Dreamhack machine. We were previously using 2.20, which is still installed but in such a way that the later version should take precedence.

As this is a core module for Dreamwidth, it's recommended that you restart Apache when possible. Things won't break just yet if you don't (since the old files aren't gone just yet), but according to my sources, the Dreamwidth codebase will require this new version of Template Toolkit soon, so things may break in the future.

As always, if anything breaks on the Dreamhack machine because of this change, please comment to let me know, or open a GitHub issue.

[edit 2014-12-07: Fix a typo.]
skud: (Default)
[personal profile] skud
If I recall correctly, there's a bot that assigns github issues to people if they say "claimed" or similar in the issue comments.

Can someone point me to the code/setup/whatever for that bot?
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
For a test, I need to have an expunged user on my dreamhack. I don't intend to wait 2 months for that test, so I'm planning to tweak the existing process. From my reading of the source code of the 3 programs listed in http://wiki.dreamwidth.net/wiki/index.php/Purging_deleted_users, I think what I want is something like:
bin/moveucluster.pl --delete --expungedel <username> 0
with a version of bin/moveucluster.pl modified to remove the built-in delay. Before I start trying and maybe break my database in subtle ways, can someone confirm I'm on the right track?
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.
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!

Profile

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

March 2015

S M T W T F S
1234567
89 1011121314
15161718192021
22232425262728
2930 31    

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 31st, 2015 09:41 am
Powered by Dreamwidth Studios