Skip to main content

Home/ The Meth Lab/ Contents contributed and discussions participated by bkozlek

Contents contributed and discussions participated by bkozlek

bkozlek

Open Atrium - 2 views

  • Open Atrium is a team collaboration tool with a kick of open source hotness.
  •  
    open source intranet / collaboration tools built on drupal
bkozlek

Google Dissolves Search Group Internally, Now Called "Knowledge" - 2 views

  • it’s to make sure that the team inside Google understands that they aren’t just working on search. It’s not just about organization, it’s about enhancement of knowledge.
bkozlek

YouTube - Discussions in Google Docs - 1 views

shared by bkozlek on 16 Mar 11 - No Cached
  •  
    Killer new discussion features in google docs.
bkozlek

Substance (Developer Preview) - 1 views

  •  
    Open source software for web based document authoring, publishing, and annotating. Looks very slick. It could potentially be brought in house.
  •  
    Substance uses server-side javascript, so it is not a plug right into existing webspace. That doesn't mean it can't be run at penn state.
bkozlek

Co.Support.Us - 0 views

shared by bkozlek on 16 Feb 11 - No Cached
  •  
    outsource the writing of help documentation and customer support. Founded by former 37signals-er.
bkozlek

Movable Type 5.1 Beta 1 - 0 views

  •  
    new version of MT. Not sure if it is ready for us to migrate yet or not. Of particular interest is the drag n drop reordering of folders and categories (although not pages and entries? hmm?)
bkozlek

Continuous Deployment - 0 views

  • Continuous deployment is the idea that you push out changes to your code base all the time instead of doing large builds and pushing out big chunks of code.
  • At Etsy, they push out code about 25 times per day. It has worked out very well for Etsy and has led to faster cycles, improved morale, and a more stable and reliable web service.
  • I asked how to roll back the changes. He said "we don't roll back, we fix the code."
  •  
    Continuous deployment is not just a technical detail. I think it informs the character of the web service. It allows the web service to react to the needs of the users on a constant basis. It also makes being agile easier, as managing larger releases incurs overhead with each new release. Tim O'Reilly defined this ability of software to constantly be updated as one of the hallmarks of web 2.0. Large releases are vestigial of a time when software had to be shipped to and installed by customers.
bkozlek

A network of networks - 0 views

  •  
    Gardner Campbell further expounds on his "Personal Cyberinfrastructure" ideas for UMW's ds106 open course.
bkozlek

No More Digital Facelifts: Thinking the Unthinkable About Open Educational Experiences - 1 views

  •  
    Gardner Campbell's Presentation at open ed 2009 where he further expounds on his notion of Personal Cyberinfrastructure
bkozlek

A Personal Cyberinfrastructure (EDUCAUSE Review) | EDUCAUSE - 0 views

  • Just as the real computing revolution didn't happen until the computer became truly personal, the real IT revolution in teaching and learning won't happen until each student builds a personal cyberinfrastructure that is as thoughtfully, rigorously, and expressively composed as an excellent essay or an ingenious experiment.
  • Pointing students to data buckets and conduits we've already made for them won't do. Templates and training wheels may be necessary for a while, but by the time students get to college, those aids all too regularly turn into hindrances. For students who have relied on these aids, the freedom to explore and create is the last thing on their minds, so deeply has it been discouraged.
  • To provide students the guidance they need to reach these goals, faculty and staff must be willing to lead by example — to demonstrate and discuss, as fellow learners, how they have created and connected their own personal cyberinfrastructures. Like the students, faculty and staff must awaken their own self-efficacy within the myriad creative possibilities that emerge from the new web.
  •  
    Gardner Campbell's Ideas about personal cyberinfrastructure. How do these ideas relate to the platforms we provide or should provide at PSU?
bkozlek

How did WordPress win? - 2 views

  •  
    An interesting look at movable type vs wordpress from a former insider at six apart.
  •  
    The grass is always greener in some respects. Ultimately MT plays in our infrastructure and scales the way we need. Really the difference in the communities around MT and WP is one of the biggest differences. This article outlines how those differences evolved.
bkozlek

Homepage - IST432_FA2010_Team4 - Confluence - 2 views

  •  
    I stumbled upon this example of a student project created with confluence at PSU.
bkozlek

What Is Web 2.0 - 5 views

  • So fundamental is the shift from software as artifact to software as service that the software will cease to perform unless it is maintained on a daily basis.
  • It's also no accident that scripting languages such as Perl, Python, PHP, and now Ruby, play such a large role at web 2.0 companies. Perl was famously described by Hassan Schroeder, Sun's first webmaster, as "the duct tape of the internet." Dynamic languages (often called scripting languages and looked down on by the software engineers of the era of software artifacts) are the tool of choice for system and network administrators, as well as application developers building dynamic systems that require constant change.
  • Users must be treated as co-developers, in a reflection of open source development practices (even if the software in question is unlikely to be released under an open source license.) The open source dictum, "release early and release often" in fact has morphed into an even more radical position, "the perpetual beta," in which the product is developed in the open, with new features slipstreamed in on a monthly, weekly, or even daily basis.
  • ...2 more annotations...
  • Cal Henderson, the lead developer of Flickr, recently revealed that they deploy new builds up to every half hour.
  • Support lightweight programming models that allow for loosely coupled systems. The complexity of the corporate-sponsored web services stack is designed to enable tight coupling. While this is necessary in many cases, many of the most interesting applications can indeed remain loosely coupled, and even fragile. The Web 2.0 mindset is very different from the traditional IT mindset! Think syndication, not coordination. Simple web services, like RSS and REST-based web services, are about syndicating data outwards, not controlling what happens when it gets to the other end of the connection. This idea is fundamental to the internet itself, a reflection of what is known as the end-to-end principle. Design for "hackability" and remixability. Systems like the original web, RSS, and AJAX all have this in common: the barriers to re-use are extremely low. Much of the useful software is actually open source, but even when it isn't, there is little in the way of intellectual property protection. The web browser's "View Source" option made it possible for any user to copy any other user's web page; RSS was designed to empower the user to view the content he or she wants, when it's wanted, not at the behest of the information provider; the most successful web services are those that have been easiest to take in new directions unimagined by their creators. The phrase "some rights reserved," which was popularized by the Creative Commons to contrast with the more typical "all rights reserved," is a useful guidepost.
  •  
    in revisiting this classic from 2005, it became obvious to me that much of higher ed is still stuck in a pre-web or at least web 1.0 model of software as artifact, and not software as service. 
  •  
    What strikes me about it this time is that there is a connection between the then new technological methodologies and infrastructures and the new architecture of participation.
  •  
    I don't think the emergence of app/app store models challenges the thinking in the piece, but it does extend the concepts it presents. The app developing tool kits is another way to bring the web service / data/ participatory experience to mobile devices. The web at large wasn't up to the challenge - apps provide a better experience than web interfaces on mobile, or at least it can be argued. HTML/CSS/Javascript versus iOS sdk/Obj C - different ways of writing an interface to the same web back ends. They each have their strengths and weaknesses. Another way it extends the thinking in the piece is that now participating is happening on a more massive scale with people able to participate on the go, not just when they are at their desk. It really raises it to the next level. The amount of data and content being shared continues to mushroom. Participating on the go as become the norm for lead users. I think there is an expectation from the community that mobile access will work well.
bkozlek

Google Apps Marketplace Gets An Education Category - 0 views

  • Aimed for Google’s 10 million Google Apps for Education users, the category offers over 20 applications from 19 vendors including specialized apps for schools and universities such as social learning game Grockit, grading software LearnBoost, math teaching tool DreamBox, design apps Aviary and more.
  •  
    disaggregation of education software services built on a common platform
bkozlek

Live@Edu grows, evolves into Office 365 for Education, leapfrogs Google Apps for Educat... - 3 views

  •  
    office 365 seems to be a new offering that bundles licenses for the desktop version of office along with the cloud-based versions. The author of the zdnet article seems to feel that bundling the desktop versions is a big plus, but I don't really see it. I think one of the pluses of google docs is that it is much more simple and easier to use than ms word. 
1 - 15 of 15
Showing 20 items per page