ISSANI GNUSL3S LINUX OS


  • Description : ISSANI GNUSL3S LINUX OS provides a rare and huge collection of pre-installed software, including a well-organised graphical user interface and useful recovery tools for system administrators. A full range of development tools, editors, and current libraries is included for users who wish to develop or compile additional software. With this distribution you just boot from the DVD and you have a fully functional Linux OS with open source applications targeted at the molecular biologist as it comes bundled with bioinformatics applications, such as EMBOSS, Primer3, and other software. It contains an extensive set of software tools used by IT security professionals for penetration testing and vulnerability analysis. It is also designed to be used as an instant home server, i.e. it comes with pre-configured tools and applications that turn a personal computer into a home server. This distribution also integrates various unofficial network drivers into the Linux kernel, thus providing out-of-the-box support for a large number of wired and wireless network cards.
  • Category : Desktop, Development, Live Medium, Scientific, Forensics, Server, Security, Specialist, Rescue
  • Desktop : KDE, XFce, Fluxbox, IceWM
  • Based on : Slackware, SLAX, Alixe, Davix, OpenFOAM, SMS
  • Version : 10.05.xx
  • Architecture : i486 (32 bit)
  • Edition : * Bloatware Edition *
  • ISO Download Link (torrent) : project suspended
  • Origin : Goa, India
  • Status : 55%

Note: Contents are subject to change prior to release.

ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS
ISSANI GNUSL3S LINUX OS

Typo3 Reference Manuals – A Google Chrome Extension

Following is the link to *my first* google extension.

It’s a collections of Typo3 reference manuals taken straight from typo3.org website.

It’s not nearly what I’d call a cool extension, but hey it helps. :)

Anyway, this google chrome extension is for :

  • Those who don’t have good internet connection. Link in India.
  • And those who don’t like to go away from the browser to read or search something in the typo3 swx reference manuals.
Ok, so heres the link :  http://projects.issani.in/chrome/ext/t3refmans.crx

If you’re wondering why I didn’t put this on Google Chrome Extension Directory, its b’coz I couldn’t. The file size is 19.86MB. And Google has set the extension size limit to 10MB. But if you got any solution let me know.

Tip: use ctrl+F or F3 to search.

SVN – revision control – slides – pdf

SVN – revision control

Download pdf : http://docs.issani.in/dump/svn-tuts-100217-v2.pdf
Coordinating projects
Problem: How to coordinate and synchronize code
between multiple developers on a project?
– Work on the same computer, take turns coding
Nah…
– Send files by e-mail or put them online. Lots of
manual work.
– Put files on a shared disk. Files get overwritten or
deleted. Lots of direct coordination.
– In short: Error prone and inefficient.
What is a version control system?
A repository of files with monitored
access to keep track of who and what
changes were made to files
Version tracking
Collaboration and sharing files
Historical information
Retrieve past versions
Manage branches
Why use it?
In code development, a version control
system is, at this point, almost mandatory
With multiple developers impossible to keep
track of versions with out it
Must be able to roll back a version if a test
suite fails
Must be able to tag software releases
Coordinating projects (solution)
Solution: A source code management (scm) tool.
– Repository: Code stored on a central server.
– Working copy: The developer checks out a copy
of the code in the repository to his/her computer.
– Revision history: Every change to every file is
logged in a database. Can be rollbacked.
– Conflict handling: What happens when two
developers change the same file? The same line?
Basic Work Cycle
Checkout a working copy
Update a working copy
Make changes
Examine your changes
Commit your changes
Some Commands
Subversion commands communicating with the server:
svn checkout …
svn commit
Offline Subversion commands:
svn add
svn delete
svn status     (high level compare)
svn diff    (low level compare)
svn rename
svn move
More information:
svn help [cmd]
Create Repository
Creating a repository:
/home/shafiqissani> svnadmin create assignment1
…results in a repository directory:
/home/shafiqissani/assignment1
What’s inside the repository?
/conf/…
/dav/…
/db/…
/format
/hooks/…
/locks/…
/README.txt
Basic commands
svn checkout <source>
A projectA/file1
A projectA/file2
A projectA/file3
Checked out revision 28.
$
svn status
$ svn status
M projectA/file1
?    projectA/file4
$
Basic commands
svn add/delete/copy/move <filename>
$ svn add file4
A file4
$
svn commit <message>
$ svn commit –m “fix another bugs”
Sending         file1
Adding          file4
Transmitting file data.
Committed revision 29.
$
Basic commands
svn log
$ svn log
——————————————————————————–
r29 | shafiq | Tue, 26 Dec 2006 18:03:46 +0900 | 1 line
fix another bugs
——————————————————————————–
r28 | shafiq | Mon, 25 Dec 2006 13:01:24 +0900 | 1 line
Fixed some bugs.
——————————————————————————–
r27 | jissani | Mon, 25 Dec 2006 12:58:24 +0900 | 1 line
Some works.
Basic Commands
svn update
$ svn update
U file1
A file4
Updated to revision 29
$ svn update –r28
U file1
D file4
Updated to revision 28
$
Trunk, Branches, Tags
SVN project directories are structured by convention with three top-level
directories:
trunk/
Represents the ‘main line’ of development with an entire copy of the
project.
branches/
Contains subdirectories, each holding an entire copy of the project
Each branch constitutes a significant enhancement to the project that
can be worked on independently.
tags/
Contains subdirectories, each containing one snapshot of the project.
Each snapshot represents a “public release” or other archival
configuration of the project.
Trunk vs. Branch
Trunk represents the stable version of the
system. It should always work, without errors
ofcourse.
Branches represent temporary development
streams to implement significant new features.
This allows commits to repository without breaking
the trunk (stable) version.
Branches may contain error/warnings etc.
Queries / Feedback
email@shafiq.in

SVN – revision control             email@shafiq.in  Coordinating projects●   Problem: How to coordinate and synchronize code    between multiple developers on a project?   – Work on the same computer, take turns coding    Nah…     – Send files by e-mail or put them online. Lots of    manual work.    – Put files on a shared disk. Files get overwritten or    deleted. Lots of direct coordination.   – In short: Error prone and inefficient. What is a version control system?  A repository of files with monitored  access to keep track of who and what  changes were made to files     Version tracking        Collaboration and sharing files        Historical information        Retrieve past versions        Manage branches   Why use it?  In code development, a version control  system is, at this point, almost mandatory     With multiple developers impossible to keep        track of versions with out it     Must be able to roll back a version if a test        suite fails     Must be able to tag software releases    Coordinating projects (solution)  Solution: A source code management (scm) tool.     – Repository: Code stored on a central server.        – Working copy: The developer checks out a copy        of the code in the repository to his/her computer.     – Revision history: Every change to every file is        logged in a database. Can be rollbacked.     – Conflict handling: What happens when two        developers change the same file? The same line? Basic Work Cycle  Checkout a working copy  Update a working copy  Make changes  Examine your changes  Commit your changesSome Commands  Subversion commands communicating with the server:       svn checkout …          svn commit     Offline Subversion commands:       svn add          svn delete          svn status     (high level compare)          svn diff    (low level compare)          svn rename          svn move           …     More information:       svn help [cmd]   Create Repository  Creating a repository:     /home/shafiqissani> svnadmin create assignment1        …results in a repository directory:     /home/shafiqissani/assignment1  What’s inside the repository?     /conf/…        /dav/…        /db/…        /format        /hooks/…        /locks/…        /README.txt   Basic commandssvn checkout <source>       $ svn checkout http://url/repos/projectA       A projectA/file1       A projectA/file2       A projectA/file3       Checked out revision 28.       $svn status       $ svn status       M projectA/file1       ?    projectA/file4       $Basic commandssvn add/delete/copy/move <filename>      $ svn add file4      A file4      $svn commit <message>      $ svn commit –m “fix another bugs”      Sending         file1      Adding          file4      Transmitting file data.      Committed revision 29.      $Basic commandssvn log       $ svn log       ——————————————————————————–       r29 | shafiq | Tue, 26 Dec 2006 18:03:46 +0900 | 1 line       fix another bugs       ——————————————————————————–       r28 | shafiq | Mon, 25 Dec 2006 13:01:24 +0900 | 1 line       Fixed some bugs.       ——————————————————————————–       r27 | jissani | Mon, 25 Dec 2006 12:58:24 +0900 | 1 line       Some works.Basic Commandssvn update      $ svn update      U file1      A file4      Updated to revision 29      $ svn update –r28      U file1      D file4      Updated to revision 28      $ Trunk, Branches, Tags  SVN project directories are structured by convention with three top-level  directories:  trunk/      Represents the ‘main line’ of development with an entire copy of the          project.  branches/      Contains subdirectories, each holding an entire copy of the project          Each branch constitutes a significant enhancement to the project that          can be worked on independently.  tags/      Contains subdirectories, each containing one snapshot of the project.          Each snapshot represents a “public release” or other archival          configuration of the project.Trunk vs. Branch  Trunk represents the stable version of the  system. It should always work, without errors  ofcourse.  Branches represent temporary development  streams to implement significant new features.     This allows commits to repository without breaking        the trunk (stable) version.     Branches may contain error/warnings etc.   Queries / Feedback  email@shafiq.in

Scrum Development Model – steps

Scrum Development Model

Download pdf : http://docs.issani.in/dump/scrum-tuts-100219-v2.1.pdf
Required Steps
1) Get your backlog in order
1. Involve stakeholders
2. Create list of product actions
3. Prioritize this list
4. Get list confirmed with product owner
5. Discuss list with team
2) As a team, estimate your Product backlog
1. Provide a high-level guess/estimate
2. Product owner reviews priorities
3) As a team, plan Sprint requirements
1. Call a sprint planning meeting
2. Ensure that whole team attends
3. Decide sprint duration (weekly/monthly)
4. Select target backlog items for sprint
1. Choose high priority items first
5. Clarify sprint requirements
1. Methodically go through each item at a time
2. Ask product owner to present each item from functional perspective
3. Discuss the items in detail
5. Write requirements by feature
4) As a team, plan Sprint tasks
1. Break requirements into tasks
1. Go through each backlog item
2. Break these tasks down further
3. Include all items to make the Product backlog item 100% complete
2. Estimate tasks in hours
3. Commit to the Sprint backlog
1. remove lower items (according) if exceeding sprint capacity
4. Identify stretch/delayable tasks
5) Create an effective collaborative workspace
1. use some software tool or the traditional whiteboard
Required Steps (contd.)
6) ‘Sprint’ to achieve the Sprint goal
1. Understand that the sprint duration is fixed
2. If you finish early, include more scope
3. If you’re behind reduce scope
4. Ensure that you complete one feature at a time to 100% (that includes
testing)
7) Optimize Stand up meetings (Scrums)
1. Scrum master should ensure that impedances are removed
2. Keep meetings to 15 minutes maximum
3. Ensure everyone answers 3 questions
1. what u did since last scrum
2. what you’re planning to finish by next scrum
3. Any blocks or impediments that are in their way
4. Note that the Daily Scrum is not a status meeting to report to a manager
8) Track progress with a Daily burndown chart
1. Update estimated time to complete (ETC) daily
2. Ensure individuals update their own ETC before daily scrum
3. Plot progress visually on graph (burndown chart)
9) Finish on schedule
10) Review
1. At the end of the sprint, hold a sprint review meeting
2. Team members demo the software
3. Review the burndown chart
4. Discuss what went well
5. Discuss what could be improved and improvements for the next sprint

Scrum DevelopmentModel        email@shafiq.in Required Steps1) Get your backlog in order  1. Involve stakeholders  2. Create list of product actions  3. Prioritize this list  4. Get list confirmed with product owner  5. Discuss list with team2) As a team, estimate your Product backlog  1. Provide a high-level guess/estimate  2. Product owner reviews priorities3) As a team, plan Sprint requirements  1. Call a sprint planning meeting  2. Ensure that whole team attends  3. Decide sprint duration (weekly/monthly)  4. Select target backlog items for sprint     1. Choose high priority items first  5. Clarify sprint requirements     1. Methodically go through each item at a time     2. Ask product owner to present each item from functional perspective     3. Discuss the items in detail     5. Write requirements by feature4) As a team, plan Sprint tasks  1. Break requirements into tasks     1. Go through each backlog item     2. Break these tasks down further     3. Include all items to make the Product backlog item 100% complete  2. Estimate tasks in hours  3. Commit to the Sprint backlog     1. remove lower items (according) if exceeding sprint capacity  4. Identify stretch/delayable tasks5) Create an effective collaborative workspace  1. use some software tool or the traditional whiteboard Required Steps (contd.)6) ‘Sprint’ to achieve the Sprint goal  1. Understand that the sprint duration is fixed  2. If you finish early, include more scope  3. If you’re behind reduce scope  4. Ensure that you complete one feature at a time to 100% (that includestesting)7) Optimize Stand up meetings (Scrums)  1. Scrum master should ensure that impedances are removed  2. Keep meetings to 15 minutes maximum  3. Ensure everyone answers 3 questions     1. what u did since last scrum     2. what you’re planning to finish by next scrum     3. Any blocks or impediments that are in their way  4. Note that the Daily Scrum is not a status meeting to report to a manager8) Track progress with a Daily burndown chart  1. Update estimated time to complete (ETC) daily  2. Ensure individuals update their own ETC before daily scrum  3. Plot progress visually on graph (burndown chart)9) Finish on schedule10) Review   1. At the end of the sprint, hold a sprint review meeting   2. Team members demo the software   3. Review the burndown chart   4. Discuss what went well   5. Discuss what could be improved and improvements for the next sprint